Describe the bug
After performing a backup with Pika on Bluefin, I was unable to mount the archive and it says
Failed to make archives available for browsing.
fusermount3: mount failed: Operation not permitted
What did you expect to happen?
The backup should mount as a browseable directory.
Output of bootc status
apiVersion: org.containers.bootc/v1
kind: BootcHost
metadata:
name: host
spec:
image:
image: ghcr.io/ublue-os/bluefin-dx:gts
transport: registry
signature: containerPolicy
bootOrder: default
status:
staged: null
booted:
image:
image:
image: ghcr.io/ublue-os/bluefin-dx:gts
transport: registry
signature: containerPolicy
version: gts-40.20250126
timestamp: 2025-01-26T06:04:45Z
imageDigest: sha256:0d981a30f0371a92fb554f8949f1482cb0d8d61924368b31c0e3ed8fb7509097
cachedUpdate: null
incompatible: false
pinned: false
store: ostreeContainer
ostree:
checksum: 136794e542aa6843045fc6dd51bf1d42266aac61d0e7604272ed19bfde03b073
deploySerial: 0
rollback:
image:
image:
image: ghcr.io/ublue-os/bluefin-dx:gts
transport: registry
signature: containerPolicy
version: gts-40.20250119
timestamp: 2025-01-19T06:04:07Z
imageDigest: sha256:749767a4d1adf23a9f04d3e2ce596b355fe1acb1d7dc917434537bba560ab38d
cachedUpdate:
image:
image: ghcr.io/ublue-os/bluefin-dx:gts
transport: registry
signature: containerPolicy
version: gts-40.20250126
timestamp: 2025-01-26T06:04:45Z
imageDigest: sha256:0d981a30f0371a92fb554f8949f1482cb0d8d61924368b31c0e3ed8fb7509097
incompatible: false
pinned: false
store: ostreeContainer
ostree:
checksum: c7290144aabebd142e74f7328330689bb5f99a9bbdb9e45d5e21edc9c7b5c46e
deploySerial: 0
rollbackQueued: false
type: bootcHost
Output of groups
Extra information or context
According to the issue here
https://gitlab.gnome.org/World/pika-backup/-/issues/527#note_2344721
It works fine on plain Silverblue. Has a fuse dependency been removed?
Describe the bug
After performing a backup with Pika on Bluefin, I was unable to mount the archive and it says
What did you expect to happen?
The backup should mount as a browseable directory.
Output of
bootc statusapiVersion: org.containers.bootc/v1 kind: BootcHost metadata: name: host spec: image: image: ghcr.io/ublue-os/bluefin-dx:gts transport: registry signature: containerPolicy bootOrder: default status: staged: null booted: image: image: image: ghcr.io/ublue-os/bluefin-dx:gts transport: registry signature: containerPolicy version: gts-40.20250126 timestamp: 2025-01-26T06:04:45Z imageDigest: sha256:0d981a30f0371a92fb554f8949f1482cb0d8d61924368b31c0e3ed8fb7509097 cachedUpdate: null incompatible: false pinned: false store: ostreeContainer ostree: checksum: 136794e542aa6843045fc6dd51bf1d42266aac61d0e7604272ed19bfde03b073 deploySerial: 0 rollback: image: image: image: ghcr.io/ublue-os/bluefin-dx:gts transport: registry signature: containerPolicy version: gts-40.20250119 timestamp: 2025-01-19T06:04:07Z imageDigest: sha256:749767a4d1adf23a9f04d3e2ce596b355fe1acb1d7dc917434537bba560ab38d cachedUpdate: image: image: ghcr.io/ublue-os/bluefin-dx:gts transport: registry signature: containerPolicy version: gts-40.20250126 timestamp: 2025-01-26T06:04:45Z imageDigest: sha256:0d981a30f0371a92fb554f8949f1482cb0d8d61924368b31c0e3ed8fb7509097 incompatible: false pinned: false store: ostreeContainer ostree: checksum: c7290144aabebd142e74f7328330689bb5f99a9bbdb9e45d5e21edc9c7b5c46e deploySerial: 0 rollbackQueued: false type: bootcHostOutput of
groupsExtra information or context
According to the issue here
https://gitlab.gnome.org/World/pika-backup/-/issues/527#note_2344721
It works fine on plain Silverblue. Has a fuse dependency been removed?