Unable to mount squashfs
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
I'm attempting to mount squashfs images inside a sysbox runtime'd Kubernetes pod as a dependency of our Bazel build system.
➜ sudo mount img.sqfs /mnt/img -t squashfs -o loop
mount: /mnt/img: failed to setup loop device for img.sqfs.
And going down a little deeper into losetup, I see..
➜ sudo strace losetup --find --show img.sqfs
...
openat(AT_FDCWD, "/home/admin/img.sqfs", O_RDWR|O_CLOEXEC) = 4
openat(AT_FDCWD, "/dev/loop0", O_RDWR|O_CLOEXEC) = -1 EACCES (Permission denied)
...
I'd like to understand if this is a bug, configuration issue or limitation of sysbox. Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the mount and losetup commands inside a Sysbox runtime Kubernetes pod, then inspect the /dev/loop0 access failure and runtime configuration. Done means establishing whether this is a bug, required configuration, or a Sysbox limitation, with the supported path documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, linux
- Domain
- infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100