Podman ps is hanging for rootless container #10269
Comments
openshift-ci-robot
added
the
kind/bug
|
A friendly reminder that this issue had no activity for 30 days. |
|
@rugk Are you still seeing this issue? |
|
I have not seen it again so far. |
|
Ok I am going to close until we can get a reproducer, reopen if it happens again. |
|
This happens again as soon as I have switched to Or okay, it does not hang forever, but takes literally 30s or so to complete, even simple commands which take milliseconds like Ah, and after the first command is through and takes some seconds, the subsequent CLi commands are as fast as always. It is reproducible currently, though. (Different system though) System$ podman info
host:
arch: amd64
buildahVersion: 1.26.1
cgroupControllers:
- memory
- pids
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.1.0-2.fc36.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.1.0, commit: '
cpuUtilization:
idlePercent: 89.14
systemPercent: 6.16
userPercent: 4.7
cpus: 4
distribution:
distribution: fedora
variant: coreos
version: "36"
eventLogger: journald
hostname: minipure
idMappings:
gidmap:
- container_id: 0
host_id: 1002
size: 1
- container_id: 1
host_id: 231072
size: 65536
uidmap:
- container_id: 0
host_id: 1002
size: 1
- container_id: 1
host_id: 231072
size: 65536
kernel: 5.17.9-300.fc36.x86_64
linkmode: dynamic
logDriver: journald
memFree: 64179392512
memTotal: 67301498880
networkBackend: netavark
ociRuntime:
name: crun
package: crun-1.4.4-1.fc36.x86_64
path: /usr/bin/crun
version: |-
crun version 1.4.4
commit: 6521fcc5806f20f6187eb933f9f45130c86da230
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
os: linux
remoteSocket:
path: /run/user/1002/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: true
serviceIsRemote: false
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.2.0-0.2.beta.0.fc36.x86_64
version: |-
slirp4netns version 1.2.0-beta.0
commit: 477db14a24ff1a3de3a705e51ca2c4c1fe3dda64
libslirp: 4.6.1
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.3
swapFree: 4294963200
swapTotal: 4294963200
uptime: 7m 5.75s
plugins:
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
volume:
- local
registries:
search:
- registry.fedoraproject.org
- registry.access.redhat.com
- docker.io
- quay.io
store:
configFile: /var/home/**USER**/.config/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions: {}
graphRoot: /var/home/**USER**/.local/share/containers/storage
graphRootAllocated: 999650168832
graphRootUsed: 38050099200
graphStatus:
Backing Filesystem: btrfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
imageCopyTmpDir: /var/tmp
imageStore:
number: 10
runRoot: /run/user/1002/containers
volumePath: /var/home/**USER**/.local/share/containers/storage/volumes
version:
APIVersion: 4.1.0
Built: 1651853754
BuiltTime: Fri May 6 18:15:54 2022
GitCommit: ""
GoVersion: go1.18
Os: linux
OsArch: linux/amd64
Version: 4.1.0Fedora CoreOS v36.20220522.3.0 |
github-actions
bot
added
the
locked - please file new issue/PR
/kind bug
Description
When I start a container with
podman-deployorpodman start -ait does not output anything or so. And further podman commands then also hang (likepodman ps).Steps to reproduce the issue:
I have a simple NodeJS container similar to this one:
https://nodejs.org/en/docs/guides/nodejs-docker-webapp/
Start it with podman or
podman-compose.podman psin a new window:Describe the results you received:
Podman ps is stuck. As you can see above, I can only exist with
Ctrl+C.This is very similar to other issues I have found, but all seem to be closed or so:
https://bugzilla.redhat.com/show_bug.cgi?id=1732525
#8710
#9228
Describe the results you expected:
When you run
podman psas root, it works. So don’t block ever. At least show me an error.Also it works when I run
podman psas root, and it works when the other process running the container is also (not) stuck(?).Also as soon as stop (Ctrl+C) the other process, the
podman psprocess continues.Additional information you deem important (e.g. issue happens only occasionally):
I tried to reproduce it with some other more simple container like the NodeJS example mentioned earlier, but it does not work.
Also happens to other podman commands.
Output of
podman version:Output of
podman info --debug:Package info (e.g. output of
rpm -q podmanorapt 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)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Physical, Raspberry Pi
Fedora Iot 34
This is quite a fresh system/installation.
Also reproduced in x64 Fedora Workstation 34.
As suggested in #9228, which sounds very similar:
The text was updated successfully, but these errors were encountered: