You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initialize a containers-storage: owned by bootc, use for bound images
Initial work for: #721
- Initialize a containers-storage: instance at install time
(that defaults to empty)
- "Open" it (but do nothing with it) as part of the core CLI
operations
Further APIs and work will build on top of this.
Signed-off-by: Colin Walters <[email protected]>
Copy file name to clipboardExpand all lines: docs/src/experimental-logically-bound-images.md
+17-4Lines changed: 17 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,11 @@ This experimental feature enables an association of container "app" images to a
14
14
15
15
## Using logically bound images
16
16
17
-
Each image is defined in a [Podman Quadlet](https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html)`.image` or `.container` file. An image is selected to be bound by creating a symlink in the `/usr/lib/bootc/bound-images.d` directory pointing to a `.image` or `.container` file. With these defined, during a `bootc upgrade` or `bootc switch` the bound images defined in the new bootc image will be automatically pulled via podman.
17
+
Each image is defined in a [Podman Quadlet](https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html)`.image` or `.container` file. An image is selected to be bound by creating a symlink in the `/usr/lib/bootc/bound-images.d` directory pointing to a `.image` or `.container` file.
18
+
19
+
With these defined, during a `bootc upgrade` or `bootc switch` the bound images defined in the new bootc image will be automatically pulled into the bootc image storage, and are available to container runtimes such as podman by explicitly configuring them to point to the bootc storage as an "additional image store", via e.g.:
20
+
21
+
`podman --storage-opt=additionalimagestore=/usr/lib/bootc/storage run <image> ...`
18
22
19
23
An example Containerfile
20
24
@@ -28,8 +32,17 @@ RUN ln -s /usr/share/containers/systemd/my-app.image /usr/lib/bootc/bound-images
Images are fetched using the global bootc pull secret by default (`/etc/ostree/auth.json`). It is not yet supported to configure `PullSecret` in these image definitions.
44
+
31
45
## Limitations
32
46
33
-
- Currently, only the Image field of a `.image` or `.container` file is used to pull the image. Any other field is ignored.
34
-
- There is no cleanup during rollback.
35
-
- Images are subject to default garbage collection semantics; e.g. a background job pruning images without a running container may prune them. They can also be manually removed via e.g. podman rmi.
47
+
- Currently, only the Image field of a `.image` or `.container` file is used to pull the image; per above not even `PullSecret=` is supported.
0 commit comments