-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting containers via docker-compose fails to mount resolv.conf #11358
Comments
Can you run |
Also, out of curiousity, can you provide |
I've deleted
|
@WhyNotHugo Sorry wrong path it should be |
I tried rebooting and that hasn't fixed it. Deleting |
OK please start the server with |
Whoops, the previous comment [now deleted] was a compose file with two containers, here's the correct log:
|
OK I see the error now. I hate symlinks with bind mounts together. |
I'm glad you're seeing it, because I'm not :P |
When /etc/resolv.conf is a symlink to an absolute path use it and not join it the the previous path. [NO TESTS NEEDED] This depends on the host layout. Fixes containers#11358 Signed-off-by: Paul Holzinger <[email protected]>
PR #11360 to fix |
When /etc/resolv.conf is a symlink to an absolute path use it and not join it the the previous path. [NO TESTS NEEDED] This depends on the host layout. Fixes containers#11358 Signed-off-by: Paul Holzinger <[email protected]>
When /etc/resolv.conf is a symlink to an absolute path use it and not join it the the previous path. [NO TESTS NEEDED] This depends on the host layout. Fixes #11358 Signed-off-by: Paul Holzinger <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Should not have crashed and started the container.
Additional information you deem important (e.g. issue happens only occasionally):
#10855 seems somewhat related, but that's actually fixed in 3.3.0, and I'm seeing this issue on 3.3.0.
I've tried
rm -rf .config/cni .local/share/containers/
to make sure there's nothing stale/broken there. Still the same issue.Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Checked the guide: Yes
Latest stable version: Yes
Latest
master
: NoAdditional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: