bootc-dev / bootc-dev/bootc

composefs-native: bootc retroactively broken after attempting to switch branch

Open
#2,422 12 comments 0 reactions 1 assignee Claimed by @Johan-Liebert1 View on GitHub
triaged
Dominant language
Rust
Stars
2.3k
Forks
230
Avg merge
3d 12h
Merged PRs (30d)
38

Description

Attempted to switch from `ghcr.io/secureblue/cosmic-main-hardened:br-testing-44-uki` to `ghcr.io/secureblue/cosmic-main-hardend:uki`, after rebooting `bootc` is rendered unusable on all deployments retroactively (rebooted into the old deployment), attempting to run `status`, `upgrade` or `switch` returns:
```
hooly@fedora-desktop:~$ run0 -i bootc upgrade
jq: parse error: Invalid numeric literal at line 1, column 6
error: Upgrading composefs: Getting composefs deployment status: Getting composefs deployment status: Getting composefs deployment status: Getting composefs deployment metadata: Reading image info for deployment 994112916dd9dcfd68c5dba5efc0c0585dff421f81a9a6dfdd69641756c3b94b8bd3c78114143bad8a618a78545ddcada68a147fdf8f89bcf893836720a68254: Opening OCI image for manifest sha256:2d0432b651df916a9d16c62802cd7b4776a50c78bc43b8eaca1a099d38ca0e7d: Opening stream 'oci-manifest-sha256:2d0432b651df916a9d16c62802cd7b4776a50c78bc43b8eaca1a099d38ca0e7d': Opening ref 'streams/oci-manifest-sha256:2d0432b651df916a9d16c62802cd7b4776a50c78bc43b8eaca1a099d38ca0e7d': No such file or directory (os error 2)
[1]hooly@fedora-desktop:~$ run0 -i bootc status
jq: parse error: Invalid numeric literal at line 1, column 6
error: Status: Getting composefs deployment status: Getting composefs deployment status: Getting composefs deployment metadata: Reading image info for deployment 994112916dd9dcfd68c5dba5efc0c0585dff421f81a9a6dfdd69641756c3b94b8bd3c78114143bad8a618a78545ddcada68a147fdf8f89bcf893836720a68254: Opening OCI image for manifest sha256:2d0432b651df916a9d16c62802cd7b4776a50c78bc43b8eaca1a099d38ca0e7d: Opening stream 'oci-manifest-sha256:2d0432b651df916a9d16c62802cd7b4776a50c78bc43b8eaca1a099d38ca0e7d': Opening ref 'streams/oci-manifest-sha256:2d0432b651df916a9d16c62802cd7b4776a50c78bc43b8eaca1a099d38ca0e7d': No such file or directory (os error 2)
[1]hooly@fedora-desktop:~$ run0 -i bootc switch ghcr.io/secureblue/cosmic-main-hardened:uki
jq: parse error: Invalid numeric literal at line 1, column 6
error: Switching: Composefs Switching: Getting composefs deployment status: Getting composefs deployment status: Getting composefs deployment status: Getting composefs deployment metadata: Reading image info for deployment 994112916dd9dcfd68c5dba5efc0c0585dff421f81a9a6dfdd69641756c3b94b8bd3c78114143bad8a618a78545ddcada68a147fdf8f89bcf893836720a68254: Opening OCI image for manifest sha256:2d0432b651df916a9d16c62802cd7b4776a50c78bc43b8eaca1a099d38ca0e7d: Opening stream 'oci-manifest-sha256:2d0432b651df916a9d16c62802cd7b4776a50c78bc43b8eaca1a099d38ca0e7d': Opening ref 'streams/oci-manifest-sha256:2d0432b651df916a9d16c62802cd7b4776a50c78bc43b8eaca1a099d38ca0e7d': No such file or directory (os error 2)
[1]hooly@fedora-desktop:~$
```
Additional info:
secureblue's UKI images are sealed images with the composefs-native backend,
the jq error is motd failing because it gets no info from `bootc status`

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.