Handle relative paths in VOLUME directives
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 72.1k
- Forks
- 19.2k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 164
Description
Description
- Related to https://github.com/containerd/containerd/issues/5547
- Related to https://github.com/opencontainers/runc/issues/3944
In runc 1.0, runc started erroring out if a mount destination was a relative path.
This was changed to be just a warning here: https://github.com/opencontainers/runc/pull/3004
An issue was created to re-add the error: https://github.com/opencontainers/runc/issues/3020
As part of id-mapped mounts support, this was added back here: https://github.com/opencontainers/runc/pull/3717
We need to handle this case because we don't want to break old images or builds.
Reproduce
N/A
Expected behavior
N/A
docker version
N/A
docker info
N/A
Additional Info
No response
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
Begin with the linked containerd and runc issues and trace Moby's handling of VOLUME directives. Reproduce the relative mount-destination case described there; done means old images or builds using relative paths are not broken despite runc's validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100