After installation on a first boot, if you try to run ujust update it will fails:
jq: parse error: Invalid numeric literal at line 1, column 6
error: recipe `update` failed with exit code 5
I noticed that after install in the first boot, if i run sudo bootc status
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
● Booted image: ghcr.io/ublue-os/aurora:stable
Digest: sha256:06329495185ee898d861bb967ababb55dff58ddd8fdbe28cad625a307ea6a7e2 (amd64)
Version: 44.20260902.1 (2026-09-02T03:57:54Z)
so it seems to trip itself here
|
elif [[ "${IS_OSTREE}" == "true" ]]; then |
|
# Without password would be nice |
|
# https://github.com/bootc-dev/bootc/issues/409 |
|
STATUS=$(sudo bootc status --json | jq ".status") |
|
|
which was part of the #256
So we probably need to parse out the mount.... stuff from the status so jq gets a clean json
sudo bootc status --json
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
{"apiVersion":"org.containers.bootc/v1","kind":"BootcHost","metadata":{"name":"host"},"spec":{"bootOrder":"default","image":{"image":"ghcr.io/ublue-os/aurora:stable","signature":"containerPolicy","transport":"registry"}},"status":{"booted":{"cachedUpdate":null,"composefs":null,"downloadOnly":false,"image":{"architecture":"amd64","image":{"image":"ghcr.io/ublue-os/aurora:stable","signature":"containerPolicy","transport":"registry"},"imageDigest":"sha256:06329495185ee898d861bb967ababb55dff58ddd8fdbe28cad625a307ea6a7e2","timestamp":"2026-09-02T03:57:54Z","version":"44.20260902.1"},"incompatible":false,"ostree":{"checksum":"48ab73bb3af6cbfe502003caf92810937699d2760e35f166cc30a95ccf2ecfeb","deploySerial":0,"stateroot":"default"},"pinned":false,"softRebootCapable":true,"store":"ostreeContainer"},"readOnly":false,"rollback":null,"rollbackQueued":false,"staged":null,"type":"bootcHost","usrOverlay":null}}
This error goes away if you reboot the machine a second time after install.
ISOs that are in the dl-test bucket are affected, not the production iso on the website
After installation on a first boot, if you try to run
ujust updateit will fails:I noticed that after install in the first boot, if i run
sudo bootc statusso it seems to trip itself here
common/system_files/shared/usr/share/ublue-os/just/update.just
Lines 38 to 42 in 1a1d640
which was part of the #256
So we probably need to parse out the
mount....stuff from the status so jq gets a clean jsonsudo bootc status --json
This error goes away if you reboot the machine a second time after install.
ISOs that are in the dl-test bucket are affected, not the production iso on the website