containers/storage

imagestore is not documented in containers-storage.conf(5)

nm004 opened this issue · 7 comments

Issue Description

According to podman(1),

   --imagestore=path
       Path  of the imagestore where images are stored.  By default, the storage library stores all
       the images in the graphroot but if an imagestore is provided, then the storage library  will
       store newly pulled images in the provided imagestore and keep using the graphroot for every‐
       thing else. If the user is using the overlay driver, then the images which were already part
       of the graphroot will still be accessible.

       This  will  override  imagestore  option in containers-storage.conf(5), refer to containers-
       storage.conf(5) for more details.

But imagestore is not mentioned in containers-storage.conf(5) at all.

Steps to reproduce the issue

  1. man podman
  2. man containers-storage.conf

Describe the results you received

imagestore is not documented in containers-storage.conf(5)

Describe the results you expected

imagestore is documented in containers-storage.conf(5) if it's effective.

podman info output

OS: Fedora 38

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

No response

Additional information

No response

Another option additionalimagestores is mentioned in containers-storage.conf(5), though.

I'll check this thanks.

It is mentioned in containers-storage.conf since I have been working on rewording it this week.

But when I say man storage.conf, I see the info.

       imagestore=""
         Path of imagestore different from graphroot, by default storage library stores all images in graphroot but if imagestore is
       provided  it will store newly pulled images in provided imagestore but will keep using graphroot for everything else. If user
       is using overlay driver then images which were already part of graphroot will still be accessible (  Internally  storage  li‐
       brary will mount graphroot as an additionalImageStore to allow this behaviour ).

       A  common use case for this field is for the users who want to split the file‐system in different parts i.e disk which stores
       images vs disk used by the container created by the image.

Closing issue, continue the conversation here.

The package in Fedora38 has not include the changes of this repo yet, so it did not appear on my system. I'm sorry for disturbing you. Thank you for your support.