Sysbox 0.7.0 not working on ubuntu 26.04
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
Since upgrade from ubuntu 24.04 to ubuntu 26.04 sysbox cease to work, i got this message when trying to launch my stack with docker compose
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: failed to pre-register with sysbox-fs: failed to pre-register container with sysbox-fs: rpc error: code = Internal desc = Initialization error for container-id
And when I verify the log of sysbox-fs with journactl -u sysbox-fs I found:
sysbox-fs[20604]: 2026/04/27 23:43:05 mount helper error: fusermount3: mount failed: Permission denied
sysbox-fs[20604]: time="2026-04-27 23:43:05" level=error msg="fusermount: exit status 1"
I try several thing like reinstall sysbox even full uninstall and then reinstall, restart sysbox sysbox -fs and sysbox-mgr, reloading fuse but nothing seems to work
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
Start by reproducing the failure on Ubuntu 26.04 with the reported Docker Compose stack, then inspect the sysbox-fs and sysbox-mgr services and their journalctl output. Use the fusermount3 permission error as the first lead; done means identifying the Ubuntu compatibility or configuration cause and restoring container startup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, linux, shell, ubuntu
- Domain
- devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100