bootc
bootc copied to clipboard
containers
Boot and upgrade via container images
This will let higher level tools (Plasma Discover for example) more easily read the output of `bootc update --check --json`. --- Needs https://github.com/ostreedev/ostree-rs-ext/pull/618
When `bootc` shells out to external applications, such as during installation to sgdisk and systemd-cryptenroll, it should provide a way for the **entire exact command** to be logged or otherwise...
Right now bootc uses the naive systemd-cryptenroll default PCR selection of 7 when binding a LUKS volume. This is not ideal as shim package updates or version disagreement between installation...
- Introduce 'insecure-disable-tls-verification' parameter for skipping TLS verification; - Fix Issue: #461.
See problems described in #476 and #421 for context. The `bootc install to-disk --block-setup tpm2-luks` feature needs to provision either a systemd-cryptenroll recovery key or a default/backup password for the...
This issue tracks our "full" support for installing SELinux-enabled targets from SELinux-disabled hosts.
Run `podman run --rm --privileged --pid=host -v /:/target -v /dev:/dev -v /var/lib/containers:/var/lib/containers --security-opt label=type:unconfined_t quay.io/redhat_emp1/bootc-workflow-test:jjj0 bootc install to-existing-root` on nvidia-jetson-agx-orin board with `LVM` configured failed with error `Installing to filesystem:...
This is very similar to https://github.com/coreos/rpm-ostree/pull/1368/commits/83c942dac2fec09e5077b601438229f7da8e6c33 and later https://github.com/coreos/rpm-ostree/pull/2459 Basically...it'd be really useful to be able to see from `bootc status` the basic information about which calling process (systemd unit...
I'd resisted doing this a lot, but there are enough local dev/test scenarios where it'd be useful to be able to fetch from an insecure registry. This would probably be...
Running `bootc usoverlay` is not reflected in `bootc status` as far as I could see.