Skip to content

Commit 9fa341e

Browse files
committed
boundimages: Switch from bootc-experimental to bootc
This is a stable enough feature to be included in the primary bootc directory. Signed-off-by: Chris Kyrouac <[email protected]>
1 parent affe394 commit 9fa341e

File tree

4 files changed

+5
-6
lines changed

4 files changed

+5
-6
lines changed

Makefile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ all:
99

1010
install:
1111
install -D -m 0755 -t $(DESTDIR)$(prefix)/bin target/release/bootc
12-
install -d -m 0755 $(DESTDIR)$(prefix)/lib/bootc-experimental/bound-images.d
12+
install -d -m 0755 $(DESTDIR)$(prefix)/lib/bootc/bound-images.d
1313
install -d -m 0755 $(DESTDIR)$(prefix)/lib/bootc/kargs.d
1414
install -d -m 0755 $(DESTDIR)$(prefix)/lib/systemd/system-generators/
1515
ln -f $(DESTDIR)$(prefix)/bin/bootc $(DESTDIR)$(prefix)/lib/systemd/system-generators/bootc-systemd-generator

contrib/packaging/bootc.spec

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,6 @@ BuildRequires: libzstd-devel
3131
%{_bindir}/bootc
3232
%{_prefix}/lib/systemd/system-generators/*
3333
%{_prefix}/lib/bootc
34-
%{_prefix}/lib/bootc-experimental
3534
%{_unitdir}/*
3635
%{_mandir}/man*/bootc*
3736

docs/src/experimental-logically-bound-images.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ This experimental feature enables an association of container "app" images to a
1414

1515
## Using logically bound images
1616

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-experimental/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. 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.
1818

1919
An example Containerfile
2020

@@ -24,8 +24,8 @@ FROM quay.io/myorg/myimage:latest
2424
COPY ./my-app.image /usr/share/containers/systemd/my-app.image
2525
COPY ./another-app.container /usr/share/containers/systemd/another-app.container
2626

27-
RUN ln -s /usr/share/containers/systemd/my-app.image /usr/lib/bootc-experimental/bound-images.d/my-app.image && \
28-
ln -s /usr/share/containers/systemd/my-app.image /usr/lib/bootc-experimental/bound-images.d/my-app.image
27+
RUN ln -s /usr/share/containers/systemd/my-app.image /usr/lib/bootc/bound-images.d/my-app.image && \
28+
ln -s /usr/share/containers/systemd/my-app.image /usr/lib/bootc/bound-images.d/my-app.image
2929
```
3030

3131
## Limitations

lib/src/boundimage.rs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ use ostree_ext::sysroot::SysrootLock;
1616

1717
/// The path in a root for bound images; this directory should only contain
1818
/// symbolic links to `.container` or `.image` files.
19-
const BOUND_IMAGE_DIR: &str = "usr/lib/bootc-experimental/bound-images.d";
19+
const BOUND_IMAGE_DIR: &str = "usr/lib/bootc/bound-images.d";
2020

2121
/// A subset of data parsed from a `.image` or `.container` file with
2222
/// the minimal information necessary to fetch the image.

0 commit comments

Comments
 (0)