Sysbox v0.6.2: container with too many layers fails to start
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
A container image with a large number of layers (> 64) fails to start with Sysbox v0.6.2, on my Ubuntu Kinetic host with kernel 5.19:
$ docker run -it --rm --runtime sysbox-runc codercom/oss-dogfood:testing
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: container_linux.go:424: starting container process caused: process_linux.go:607: container init caused: process_linux.go:578: handleReqOp caused: rootfs_init_linux.go:321: setting up ID-mapped mount on path l/UBOJSLP2TWYKIG7OSQIXTK24OU (likely means idmapped mounts are not supported on the filesystem at this path ()) caused: Failed to eval symlink on : lstat l: no such file or directory: unknown.
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 failure with docker run -it --rm --runtime sysbox-runc codercom/oss-dogfood:testing on the reported Ubuntu Kinetic and kernel 5.19 environment. Start from the reported rootfs_init_linux.go and ID-mapped mount error, then trace the handling of the layer path. Done means the image with more than 64 layers starts successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, ubuntu
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100