Add support for (weakly) "lifecycle bound" podman images #559
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a working PoC implementation of part of
#128
Demo:
Example user story:
bootc upgrade
time, bootc will pre-fetch these container images into the standard/var/lib/containers/storage
locationHowever, the container images and containers can still be updated live if desired, and that's actually expected. For example, I might update a version of an app before the base image's tag.
(a bit more in e.g. https://docs.fedoraproject.org/en-US/bootc/running-containers/#_lifecycling_and_updating_containers_separate )
notes:
/var
Error: mkdir /etc/containers/networks: read-only file system
- need to fix podman to not try to create that directory