Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Storage/image handling should be configurable #132

@cyphar

Description

@cyphar

Specifically what I mean by this is that we need to make sure that we make it easy for constrained distributions to disable and enforce certain features. Namely:

  • When the image code is merged, it's likely that we're going to be downloading images from the internet by default. However, it should be possible to disable this entirely using the configuration file. Certain deployments cannot start downloading images from the internet, and can only use the images packaged with the filesystem. This brings me to my second point ...
  • It must be possible for the image code to take OCI bundles from the filesystem, and treat the filesystem as the source. This will allow for distributions to explicitly manage updating of images (as well as all of the advanced package management offered by distributions). I'm not sure how we should make the image:tag mapping work, but I think having some cache of images that distributions can put files into might work.

There's probably a few other things, but since that code hasn't been merged I haven't thought of them yet. I've just opened this so we can keep track of it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions