-
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
docker-compose times out trying to use the user socket #10857
Comments
I cannot reproduce on fedora, please run the podman service with log level debug, |
This is the full log
|
Ok my docker-compose was not up to date, upgrading it to
|
Can you try |
That prints the following
but does not terminate. Also htop shows similar CPU usage to what I observed in the beginning (just the command of the processes is |
OK, so there is an infinity loop somewhere. Do you know if this worked with 3.2.1? |
I found the bug, as a workaround please create the |
I just compiled 3.2.1 from source and #10857 (comment) works |
After creating the |
I think you have to remove the container manually with |
oh I see, thank you that worked 🎉 |
The rootless cni namespace needs a valid /etc/resolv.conf file. On some distros is a symlink to somewhere under /run. Because the kernel will follow the symlink before mounting, it is not possible to mount a file at exactly /etc/resolv.conf. We have to ensure that the link target will be available in the rootless cni mount ns. Fixes containers#10855 Also fixed a bug in the /var/lib/cni directory lookup logic. It used `filepath.Base` instead of `filepath.Dir` and thus looping infinitely. Fixes containers#10857 [NO TESTS NEEDED] Signed-off-by: Paul Holzinger <[email protected]>
The rootless cni namespace needs a valid /etc/resolv.conf file. On some distros is a symlink to somewhere under /run. Because the kernel will follow the symlink before mounting, it is not possible to mount a file at exactly /etc/resolv.conf. We have to ensure that the link target will be available in the rootless cni mount ns. Fixes containers#10855 Also fixed a bug in the /var/lib/cni directory lookup logic. It used `filepath.Base` instead of `filepath.Dir` and thus looping infinitely. Fixes containers#10857 [NO TESTS NEEDED] Signed-off-by: Paul Holzinger <[email protected]>
/kind bug
Description
When trying to start a container using docker-compose in rootless mode with podman, docker-compose hangs and podman commands run afterwards do not respond.
Steps to reproduce the issue:
systemctl --user start podman.socket
docker-compose.yml
file (for example the following)docker-compose -H unix:///run/user/1000/podman/podman.sock --log-level DEBUG up
to make docker-compose use the previously started podman socket and let it start the container as specifiedDescribe the results you received:
docker-compose hangs for 60s (the default timeout set by COMPOSE_HTTP_TIMEOUT), then errors with
UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
. Stdout gets spammed withPending: set()
while it hangs.Additionally, running podman commands (like
podman ps
, not justpodman
however) also hang / don't return any output. Looking athtop
, two processes with the command/usr/bin/podman --log-level=info system service
are using ~150% and ~90% of cpu respectively, The only way to get podman responding again is by killing those processes.Describe the results you expected:
docker-compose should start the container without any issues and podman commands should react normally after.
Additional information you deem important (e.g. issue happens only occasionally):
The issue is reproducible and happens every time.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):apt list podman
(podman installed from the Kubic Project OBS Repository as described in the install guide)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)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Physical machine, host operating system
The text was updated successfully, but these errors were encountered: