On 2020-01-31 15:11, Eric Gustavsson wrote:
Hi all,
I have unit file generated by podman running, though as soon as I run it there's issues with running any other command that needs to do something with containers. podman ps for example will be completely unresponsive and not return anything, even after waiting minutes. Not only that, but even running podman start x by itself will hang or creating new containers
This is with Fedora 30 and Kernel 5.1.8-300.fc30.x86_64
spytec@KeyraGuest1:~$ podman --version podman version 1.7.0 spytec@KeyraGuest1:~$ podman start bitwarden -a ^C spytec@KeyraGuest1:~$ sudo systemctl start bitwarden ^C spytec@KeyraGuest1:~$ sudo systemctl status bitwarden [... output omitted...] Jan 31 13:53:14 KeyraGuest1 systemd[1]: Starting Podman container-bitwarden.service... spytec@KeyraGuest1:~$ sudo systemctl stop bitwarden spytec@KeyraGuest1:~$ podman ps ^C spytec@KeyraGuest1:~$ ps auxww | grep podman spytec 1097 0.0 0.8 62816 33808 ? S 13:52 0:00 podman spytec 1171 0.0 1.3 681944 55064 ? Ssl 13:53 0:00 /usr/bin/podman start bitwarden spytec 1178 0.0 1.4 755824 56680 ? Sl 13:53 0:00 /usr/bin/podman start bitwarden spytec 1224 0.0 0.0 9360 880 pts/0 S+ 13:54 0:00 grep --color=auto podman spytec@KeyraGuest1:~$ journalctl -u bitwarden | tail -n 5 Jan 31 13:51:50 KeyraGuest1 systemd[1]: bitwarden.service: Failed with result 'exit-code'. Jan 31 13:51:50 KeyraGuest1 systemd[1]: Failed to start Podman container-bitwarden.service. Jan 31 13:53:14 KeyraGuest1 systemd[1]: Starting Podman container-bitwarden.service... Jan 31 13:54:26 KeyraGuest1 systemd[1]: bitwarden.service: Succeeded. Jan 31 13:54:26 KeyraGuest1 systemd[1]: Stopped Podman container-bitwarden.service. spytec@KeyraGuest1:~$ ps auxww | grep podman spytec 1097 0.0 0.8 62816 33808 ? S 13:52 0:00 podman spytec 1171 0.0 1.3 682008 55064 ? Ssl 13:53 0:00 /usr/bin/podman start bitwarden spytec 1178 0.0 1.4 755824 56680 ? Sl 13:53 0:00 /usr/bin/podman start bitwarden spytec 1235 0.0 0.0 9360 816 pts/0 S+ 13:55 0:00 grep --color=auto podman spytec@KeyraGuest1:~$ kill 1181 spytec@KeyraGuest1:~$ kill 1097 spytec@KeyraGuest1:~$ podman ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES baa2f3d6ed39 docker.io/bitwardenrs/server:latest /bitwarden_rs 3 weeks ago Created 0.0.0.0:8080->8080/tcp bitwarden
And creating a whole new container spytec@KeyraGuest1:~$ podman run -d --name test postgres Trying to pull docker.io/library/postgres... [... output omitted...] Writing manifest to image destination Storing signatures Error: slirp4netns failed: "/usr/bin/slirp4netns: unrecognized option '--netns-type=path'\nUsage: /usr/bin/slirp4netns [OPTION]... PID TAPNAME\nUser-mode networking for unprivileged network namespaces.\n\n-c, --configure bring up the interface\n-e, --exit-fd=FD specify the FD for terminating slirp4netns\n-r, --ready-fd=FD specify the FD to write to when the network is configured\n-m, --mtu=MTU specify MTU (default=1500, max=65521)\n--cidr=CIDR specify network address CIDR (default=10.0.2.0/24)\n--disable-host-loopback prohibit connecting to 127.0.0.1:* on the host namespace\n-a, --api-socket=PATH specify API socket path\n-6, --enable-ipv6 enable IPv6 (experimental)\n-h, --help show this help and exit\n-v, --version show version and exit\n"
Thanks,
Eric Gustavsson, RHCSA
He/Him/His
Software Engineer
Red Hat <https://www.redhat.com>
IM: Telegram: @SpyTec
E1FE 044A E0DE 127D CBCA E7C7 BD1B 8DF2 C5A1 5384 <https://www.redhat.com>
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
It seems like you have some Podman processes hanging in the background from what you sent - if you kill those, do things go back to normal, with regards to creation of new containers, `podman ps`, etc? This sounds like a hanging process that is holding a lock, preventing anything else from running. The slirp error seems like a version mismatch - what are the RPM versions of Podman and slirp4netns over there? I suspect this is not the same issue causing the hanging issue, it seems like it exits immediately which would not hold a lock (or does it not exit, and hang instead?). Thanks, Matt Heon