Skip to content

Commit 1044a45

Browse files
committed
Release 1.1.3
Mostly install time updates in this release; this fixes Anaconda support, and also makes `bootc install to-existing-root` significantly more ergonomic. Signed-off-by: Colin Walters <walters@verbum.org>
1 parent b1cb5ab commit 1044a45

17 files changed

+107
-30
lines changed

Cargo.lock

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

docs/src/man/bootc-container-lint.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,4 +23,4 @@ part of a build process; it will error if any problems are detected.
2323

2424
# VERSION
2525

26-
v1.1.0
26+
v1.1.3

docs/src/man/bootc-container.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,4 +30,4 @@ bootc-container-help(8)
3030

3131
# VERSION
3232

33-
v1.1.0
33+
v1.1.3

docs/src/man/bootc-edit.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,4 +36,4 @@ Only changes to the \`spec\` section are honored.
3636

3737
# VERSION
3838

39-
v1.1.0
39+
v1.1.3
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
# NAME
2+
3+
bootc-install-ensure-completion - Intended for use in environments that
4+
are performing an ostree-based installation, not bootc
5+
6+
# SYNOPSIS
7+
8+
**bootc install ensure-completion** \[**-h**\|**\--help**\]
9+
10+
# DESCRIPTION
11+
12+
Intended for use in environments that are performing an ostree-based
13+
installation, not bootc.
14+
15+
In this scenario the installation may be missing bootc specific features
16+
such as kernel arguments, logically bound images and more. This command
17+
can be used to attempt to reconcile. At the current time, the only
18+
tested environment is Anaconda using \`ostreecontainer\` and it is
19+
recommended to avoid usage outside of that environment. Instead, ensure
20+
your code is using \`bootc install to-filesystem\` from the start.
21+
22+
# OPTIONS
23+
24+
**-h**, **\--help**
25+
26+
: Print help (see a summary with -h)
27+
28+
# VERSION
29+
30+
v1.1.3

docs/src/man/bootc-install-print-configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,4 +27,4 @@ string-valued filesystem name suitable for passing to \`mkfs.\$type\`.
2727

2828
# VERSION
2929

30-
v1.1.0
30+
v1.1.3

docs/src/man/bootc-install-to-disk.md

Lines changed: 16 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ bootc-install-to-disk - Install to the target block device
1010
\[**\--enforce-container-sigpolicy**\] \[**\--target-ostree-remote**\]
1111
\[**\--skip-fetch-check**\] \[**\--disable-selinux**\] \[**\--karg**\]
1212
\[**\--root-ssh-authorized-keys**\] \[**\--generic-image**\]
13-
\[**\--stateroot**\] \[**\--via-loopback**\] \[**-h**\|**\--help**\]
14-
\<*DEVICE*\>
13+
\[**\--bound-images**\] \[**\--stateroot**\] \[**\--via-loopback**\]
14+
\[**-h**\|**\--help**\] \<*DEVICE*\>
1515

1616
# DESCRIPTION
1717

@@ -130,6 +130,19 @@ boot.
130130
\- All bootloader types will be installed - Changes to the system
131131
firmware will be skipped
132132

133+
**\--bound-images**=*BOUND_IMAGES* \[default: stored\]
134+
135+
: How should logically bound images be retrieved\
136+
137+
\
138+
*Possible values:*
139+
140+
> - stored: Bound images must exist in the sources root container
141+
> storage (default)
142+
>
143+
> - pull: Bound images will be pulled and stored directly in the
144+
> targets bootc container storage
145+
133146
**\--stateroot**=*STATEROOT*
134147

135148
: The stateroot name to use. Defaults to \`default\`
@@ -149,4 +162,4 @@ firmware will be skipped
149162

150163
# VERSION
151164

152-
v1.1.0
165+
v1.1.3

docs/src/man/bootc-install-to-existing-root.md

Lines changed: 20 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,9 @@ bootc-install-to-existing-root - Install to the host root filesystem
1010
\[**\--target-ostree-remote**\] \[**\--skip-fetch-check**\]
1111
\[**\--disable-selinux**\] \[**\--karg**\]
1212
\[**\--root-ssh-authorized-keys**\] \[**\--generic-image**\]
13-
\[**\--stateroot**\] \[**\--acknowledge-destructive**\]
14-
\[**-h**\|**\--help**\] \[*ROOT_PATH*\]
13+
\[**\--bound-images**\] \[**\--stateroot**\]
14+
\[**\--acknowledge-destructive**\] \[**-h**\|**\--help**\]
15+
\[*ROOT_PATH*\]
1516

1617
# DESCRIPTION
1718

@@ -115,6 +116,19 @@ boot.
115116
\- All bootloader types will be installed - Changes to the system
116117
firmware will be skipped
117118

119+
**\--bound-images**=*BOUND_IMAGES* \[default: stored\]
120+
121+
: How should logically bound images be retrieved\
122+
123+
\
124+
*Possible values:*
125+
126+
> - stored: Bound images must exist in the sources root container
127+
> storage (default)
128+
>
129+
> - pull: Bound images will be pulled and stored directly in the
130+
> targets bootc container storage
131+
118132
**\--stateroot**=*STATEROOT*
119133

120134
: The stateroot name to use. Defaults to \`default\`
@@ -129,9 +143,10 @@ firmware will be skipped
129143

130144
\[*ROOT_PATH*\] \[default: /target\]
131145

132-
: Path to the mounted root; its expected to invoke podman with \`-v
133-
/:/target\`, then supplying this argument is unnecessary
146+
: Path to the mounted root; this is now not necessary to provide.
147+
Historically it was necessary to ensure the host rootfs was mounted
148+
at here via e.g. \`-v /:/target\`
134149

135150
# VERSION
136151

137-
v1.1.0
152+
v1.1.3

docs/src/man/bootc-install-to-filesystem.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,8 @@ filesystem structure
1313
\[**\--target-ostree-remote**\] \[**\--skip-fetch-check**\]
1414
\[**\--disable-selinux**\] \[**\--karg**\]
1515
\[**\--root-ssh-authorized-keys**\] \[**\--generic-image**\]
16-
\[**\--stateroot**\] \[**-h**\|**\--help**\] \<*ROOT_PATH*\>
16+
\[**\--bound-images**\] \[**\--stateroot**\] \[**-h**\|**\--help**\]
17+
\<*ROOT_PATH*\>
1718

1819
# DESCRIPTION
1920

@@ -144,6 +145,19 @@ boot.
144145
\- All bootloader types will be installed - Changes to the system
145146
firmware will be skipped
146147

148+
**\--bound-images**=*BOUND_IMAGES* \[default: stored\]
149+
150+
: How should logically bound images be retrieved\
151+
152+
\
153+
*Possible values:*
154+
155+
> - stored: Bound images must exist in the sources root container
156+
> storage (default)
157+
>
158+
> - pull: Bound images will be pulled and stored directly in the
159+
> targets bootc container storage
160+
147161
**\--stateroot**=*STATEROOT*
148162

149163
: The stateroot name to use. Defaults to \`default\`
@@ -161,4 +175,4 @@ mounting. To override this, use \`\--root-mount-spec\`.
161175

162176
# VERSION
163177

164-
v1.1.0
178+
v1.1.3

docs/src/man/bootc-install.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ bootc-install - Install the running container to a target
1010

1111
Install the running container to a target.
1212

13-
\## Understanding installations
13+
## Understanding installations
1414

1515
OCI containers are effectively layers of tarballs with JSON for
1616
metadata; they cannot be booted directly. The \`bootc install\` flow is
@@ -48,6 +48,11 @@ bootc-install-to-existing-root(8)
4848

4949
: Install to the host root filesystem
5050

51+
bootc-install-ensure-completion(8)
52+
53+
: Intended for use in environments that are performing an ostree-based
54+
installation, not bootc
55+
5156
bootc-install-print-configuration(8)
5257

5358
: Output JSON to stdout that contains the merged installation
@@ -61,4 +66,4 @@ bootc-install-help(8)
6166

6267
# VERSION
6368

64-
v1.1.0
69+
v1.1.3

docs/src/man/bootc-rollback.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,4 +34,4 @@ rollback invocation.
3434

3535
# VERSION
3636

37-
v1.1.0
37+
v1.1.3

docs/src/man/bootc-status.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,13 @@ bootc system state. If standard output is not a terminal, output a
1616
YAML-formatted object using a schema intended to match a Kubernetes
1717
resource that describes the state of the booted system.
1818

19-
\## Parsing output via programs
19+
## Parsing output via programs
2020

2121
Either the default YAML format or \`\--format=json\` can be used. Do not
2222
attempt to explicitly parse the output of \`\--format=humanreadable\` as
2323
it will very likely change over time.
2424

25-
\## Programmatically detecting whether the system is deployed via bootc
25+
## Programmatically detecting whether the system is deployed via bootc
2626

2727
Invoke e.g. \`bootc status \--json\`, and check if \`status.booted\` is
2828
not \`null\`.
@@ -59,4 +59,4 @@ not \`null\`.
5959

6060
# VERSION
6161

62-
v1.1.0
62+
v1.1.3

docs/src/man/bootc-switch.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Target a new container image reference to boot.
1515
This is almost exactly the same operation as \`upgrade\`, but
1616
additionally changes the container image reference instead.
1717

18-
\## Usage
18+
## Usage
1919

2020
A common pattern is to have a management agent control operating system
2121
updates via container image tags; for example,
@@ -69,4 +69,4 @@ includes a default policy which requires signatures.
6969

7070
# VERSION
7171

72-
v1.1.0
72+
v1.1.3

docs/src/man/bootc-upgrade.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,4 +52,4 @@ userspace-only restart.
5252

5353
# VERSION
5454

55-
v1.1.0
55+
v1.1.3

docs/src/man/bootc-usr-overlay.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,20 +12,20 @@ will be discarded on reboot
1212
Adds a transient writable overlayfs on \`/usr\` that will be discarded
1313
on reboot.
1414

15-
\## Use cases
15+
## Use cases
1616

1717
A common pattern is wanting to use tracing/debugging tools, such as
1818
\`strace\` that may not be in the base image. A system package manager
1919
such as \`apt\` or \`dnf\` can apply changes into this transient overlay
2020
that will be discarded on reboot.
2121

22-
\## /etc and /var
22+
## /etc and /var
2323

2424
However, this command has no effect on \`/etc\` and \`/var\` - changes
2525
written there will persist. It is common for package installations to
2626
modify these directories.
2727

28-
\## Unmounting
28+
## Unmounting
2929

3030
Almost always, a system process will hold a reference to the open mount
3131
point. You can however invoke \`umount -l /usr\` to perform a \"lazy
@@ -39,4 +39,4 @@ unmount\".
3939

4040
# VERSION
4141

42-
v1.1.0
42+
v1.1.3

docs/src/man/bootc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,4 +72,4 @@ bootc-help(8)
7272

7373
# VERSION
7474

75-
v1.1.0
75+
v1.1.3

lib/Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ license = "MIT OR Apache-2.0"
55
name = "bootc-lib"
66
readme = "README.md"
77
repository = "https://github.com/containers/bootc"
8-
version = "1.1.2"
8+
version = "1.1.3"
99
# For now don't bump this above what is currently shipped in RHEL9;
1010
# also keep in sync with the version in cli.
1111
rust-version = "1.75.0"

0 commit comments

Comments
 (0)