Skip to content

Releases: containers/bootc

1.1.3

12 Dec 18:20
f4bc200
Compare
Choose a tag to compare

Install time features

Install-time work dominates here. The biggest feature work in this release is completing support for extended bootc features such as logically bound images and kernel arguments in Anaconda (taking over the now legacy ostree container image deploy) handling.
PR: #915

The second most notable change is that bootc install no longer requires any bind mounts such as -v /dev:/dev -v /var/lib/containers:/var/lib/containers to be explicitly specified.
PR: #919

Finally, we now support to-existing-root installs for systems that are already using ostree, by leveraging stateroots. The idea additionally is to aid "factory reset" scenarios.
PR: #137

Image content

We now accept images that do not have a /ostree directory at all. This is preparation for loosening our base image requirements; at the current time we recommend that people creating new base images try this out. But you should avoid trying to remove it from existing base images until support for this has propagated to the oldest release that you want to upgrade from.
PR: #887

Client side

  • bootc status has improved output. PR: #901

Internal changes

  • A large internal change that landed in this release is that the code from the ostree-rs-ext repository was merged into this one. The future of ostree-container functionality is bootc.
  • Various CI fixes and cleanups

What's Changed

New Contributors

Full Changelog: v1.1.2...v1.1.3

v1.1.3-rc.0

05 Dec 22:21
3b9f4e4
Compare
Choose a tag to compare
v1.1.3-rc.0 Pre-release
Pre-release

Install time features

Install-time work dominates here. The biggest feature work in this release is completing support for extended bootc features such as logically bound images and kernel arguments in Anaconda (taking over the now legacy ostree container image deploy) handling.
PR: #915

The second most notable change is that bootc install no longer requires any bind mounts such as -v /dev:/dev -v /var/lib/containers:/var/lib/containers to be explicitly specified.
PR: #919

Finally, we now support to-existing-root installs for systems that are already using ostree, by leveraging stateroots. The idea additionally is to aid "factory reset" scenarios.
PR: #137

Other features

  • We now accept images that do not have a /ostree directory at all. This is preparation for loosening our base image requirements. PR: #887
  • bootc status has improved output. PR: #901

Internal changes

  • A large internal change that landed in this release is that the code from the ostree-rs-ext repository was merged into this one. The future of ostree-container functionality is bootc.
  • Various CI fixes and cleanups

What's Changed

New Contributors

Full Changelog: v1.1.2...v1.1.3-rc.0

v1.1.2

05 Nov 21:34
093ddc6
Compare
Choose a tag to compare

Notable changes

We fixed several notable bugs in the ostree-container stack, which are rolled up as part of

What's Changed

New Contributors

Full Changelog: v1.1.0...v1.1.2

v1.1.0

17 Oct 01:00
49dbe70
Compare
Choose a tag to compare

Release 1.1.0

This release officially stabilizes all APIs we have. We will continue to support in-place upgrades from existing systems for the forseeable future.

Logically bound images are stable

Additionally in this release, "logically bound images" are now stable.

Notable changes

In "cli: Add a human readable format to status" from #738 the bootc status command now outputs human readable text. The machine-readable form remains accessible via e.g. bootc status --json.

Notable bugfixes

Other changes

Full Changelog: v0.1.16...v1.1.0

v0.1.16

12 Sep 18:44
858b4fb
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.1.15...v0.1.16

v0.1.15

16 Aug 14:44
a8be2a1
Compare
Choose a tag to compare

Major changes

In this release, the API and CLI is stabilized - we've generated a JSON schema and are committed to maintaining it.

You can confidently write agent or system mangement software which controls bootc either via the existing CLI (bootc upgrade/switch) or via the API bootc edit and be sure it will not break in the future.

The other big change is that our still-experimental support for logically bound images made a lot of progress. This is also likely to be stabilized soon - please give feedback! As part of this, a large internal change happened to prepare a bootc-managed container store. This is also an important next step leading us down the path of unified storage.

Full Changelog: v0.1.14...v0.1.15

Other changes

Full Changelog: v0.1.14...v0.1.15

Release v0.1.14

25 Jul 14:21
3c31d9f
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.1.13...v0.1.14

Release 0.1.13

28 Jun 20:24
321c79b
Compare
Choose a tag to compare

The primary thing this fixes is that the new /usr/lib/bootc/kargs.d files were not being honored by bootc install.

What's Changed

New Contributors

Full Changelog: v0.1.12...v0.1.13

v0.1.12

24 Jun 20:45
40c1790
Compare
Choose a tag to compare

Release 0.1.12

New features

Added support for configuring kernel arguments in container builds via the new /usr/lib/bootc/kargs.d file; these kernel arguments can be changed "day 2" via container updates. More in https://containers.github.io/bootc/building/kernel-arguments.html

New subcommand bootc container lint that can be used in container builds via e.g. RUN bootc container lint. This is intended to be a cheap command to run that will detect at build time some common problems.

Other changes

  • A variety of improvements to the documentation landed
  • This release includes changes to the default install to-disk code and partitioning layout in preparation for supporting s390x, among other architectures.

Internals

  • Significant work on testing landed, with more to come; this should increase velocity and confidence.

Individual changes

New Contributors

Full Changelog: v0.1.11...v0.1.12

0.1.11

15 May 22:51
0fb86b8
Compare
Choose a tag to compare

A few changes to install and the client, but beyond that mainly documentation and CI fixes.

install changes

  • install: Add prominent warning+timeout when targeting host root by @cgwalters in #505
  • install/baseline: Make /boot the same fs type as / by @cgwalters in #530
  • install/to-disk: Drop separate /boot by default by @cgwalters in #529

client changes

  • deploy: Add number of layers to fetch progress by @cgwalters in #524

Other changes

Full Changelog: v0.1.10...v0.1.11