--net <any network> causes "open /etc/resolv.conf: permission denied: unknown"
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
works fine without --net. Should work with --net as well.
reproduce:
# docker run --rm --runtime=sysbox-runc --net testnet alpine
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: switching Docker DNS: rootfs_linux.go:1409: writing /etc/resolv.conf caused: open /etc/resolv.conf: permission denied: unknown.
Docker version 23.0.5, build bc4487a
sysbox-runc
edition: Community Edition (CE)
version: 0.6.1
commit: 278997aab055ad6eec9e48a555b90eef877596b7
built at: Sat Apr 8 06:08:15 UTC 2023
built by: Rodny Molina
oci-specs: 1.0.2-dev
# docker run --rm --runtime=sysbox-runc alpine ls -al /etc/resolv.conf
-rw-r--r-- 1 nobody nobody 607 May 9 19:23 /etc/resolv.conf
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 docker run --rm --runtime=sysbox-runc --net testnet alpine failure with the reported Docker and sysbox-runc versions. Trace the Docker DNS handling around rootfs_linux.go:1409 and compare it with the successful run without --net. Done means the networked command starts successfully without the /etc/resolv.conf permission error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100