Can't start standard pod |container for redhat mirror-registery

Latest response

Please do not judge strictly, I'm taking the first steps.
My colleague installed a redhat mirror-registery on the host.
Three services appeared in the system, but they do not start. The standard pod tried to run on its own, the result is the same.

systemctl  list-units  | grep quay
  quay-app.service                                                                                 loaded activating auto-restart Quay Container
  quay-postgres.service                                                                            loaded activating auto-restart PostgreSQL Podman Container for Quay
  quay-redis.service                                                                               loaded activating auto-restart Redis Podman Container for Quay

I tried to look at the service log. The situation is the same with other services.

journalctl -b -f -u quay-app.service
-- Logs begin at Mon 2022-07-18 19:47:51 MSK. --
Jul 20 12:02:38 systemd[1]: quay-app.service: Scheduled restart job, restart counter is at 3.
Jul 20 12:02:38 systemd[1]: Stopped Quay Container.
Jul 20 12:02:38 systemd[1]: Starting Quay Container...
Jul 20 12:02:38 systemd[1]: Started Quay Container.
Jul 20 12:02:39 podman[3510813]: time="2022-07-20T12:02:39+03:00" level=error msg="error starting some container dependencies"
Jul 20 12:02:39 podman[3510813]: time="2022-07-20T12:02:39+03:00" level=error msg="\"failed to mount shm tmpfs \\\"/var/lib/containers/storage/overlay-containers/3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df/userdata/shm\\\": invalid argument\""
Jul 20 12:02:39 podman[3510813]: Error: error starting some containers: internal libpod error
Jul 20 12:02:39 systemd[1]: quay-app.service: Main process exited, code=exited, status=126/n/a
Jul 20 12:02:39 podman[3511032]: 4fa09992c05efc07720e0d1ecd07d8031e93b67adb4fcd13825ea004564d26b3
Jul 20 12:02:39 systemd[1]: quay-app.service: Failed with result 'exit-code'.
Jul 20 12:03:09 systemd[1]: quay-app.service: Service RestartSec=30s expired, scheduling restart.
Jul 20 12:03:09 systemd[1]: quay-app.service: Scheduled restart job, restart counter is at 4.
Jul 20 12:03:09 systemd[1]: Stopped Quay Container.
Jul 20 12:03:09 systemd[1]: Starting Quay Container...
Jul 20 12:03:09 systemd[1]: Started Quay Container.
Jul 20 12:03:10 systemd[1]: Stopping Quay Container...
Jul 20 12:03:10 podman[3511486]: time="2022-07-20T12:03:10+03:00" level=error msg="error starting some container dependencies"
Jul 20 12:03:10 podman[3511486]: time="2022-07-20T12:03:10+03:00" level=error msg="\"failed to mount shm tmpfs \\\"/var/lib/containers/storage/overlay-containers/3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df/userdata/shm\\\": invalid argument\""
Jul 20 12:03:10 podman[3511486]: Error: error starting some containers: internal libpod error
Jul 20 12:03:10 systemd[1]: quay-app.service: Main process exited, code=exited, status=126/n/a
Jul 20 12:03:10 podman[3511707]: 1b29fd992bcb3ff9646c43ff70c3afa9ebca846a7804de9719c13f48cab3e6e4
Jul 20 12:03:10 podman[3511809]: 1b29fd992bcb3ff9646c43ff70c3afa9ebca846a7804de9719c13f48cab3e6e4
Jul 20 12:03:10 systemd[1]: quay-app.service: Failed with result 'exit-code'.
Jul 20 12:03:10 systemd[1]: Stopped Quay Container.
Jul 20 12:03:10 systemd[1]: Starting Quay Container...
Jul 20 12:03:10 systemd[1]: Started Quay Container.
Jul 20 12:03:11 podman[3511991]: time="2022-07-20T12:03:11+03:00" level=error msg="error starting some container dependencies"
Jul 20 12:03:11 podman[3511991]: time="2022-07-20T12:03:11+03:00" level=error msg="\"failed to mount shm tmpfs \\\"/var/lib/containers/storage/overlay-containers/3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df/userdata/shm\\\": invalid argument\""
Jul 20 12:03:11 podman[3511991]: Error: error starting some containers: internal libpod error
Jul 20 12:03:11 systemd[1]: quay-app.service: Main process exited, code=exited, status=126/n/a
Jul 20 12:03:11 podman[3512208]: aa42268fb6c6913e90dfd348fd1f3d26c97ac6456417e33f626bb2f7ff3db98c
Jul 20 12:03:11 systemd[1]: quay-app.service: Failed with result 'exit-code'.

I tried to run at pod in debug mode and got the following result. When starting the container, the symptoms are the same

[root@ podman]# podman --log-level=debug  pod start quay-pod
INFO[0000] podman filtering at log level debug
DEBU[0000] Called start.PersistentPreRunE(podman --log-level=debug pod start quay-pod)
DEBU[0000] Merged system config "/usr/share/containers/containers.conf"
DEBU[0000] Using conmon: "/usr/bin/conmon"
DEBU[0000] Initializing boltdb state at /var/lib/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver overlay
DEBU[0000] Using graph root /var/lib/containers/storage
DEBU[0000] Using run root /run/containers/storage
DEBU[0000] Using static dir /var/lib/containers/storage/libpod
DEBU[0000] Using tmp dir /run/libpod
DEBU[0000] Using volume path /var/lib/containers/storage/volumes
DEBU[0000] Set libpod namespace to ""
DEBU[0000] [graphdriver] trying provided driver "overlay"
DEBU[0000] cached value indicated that overlay is supported
DEBU[0000] cached value indicated that metacopy is being used
DEBU[0000] cached value indicated that native-diff is not being used
INFO[0000] Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled
DEBU[0000] backingFs=xfs, projectQuotaSupported=false, useNativeDiff=false, usingMetacopy=true
DEBU[0000] Initializing event backend file
DEBU[0000] configured OCI runtime crun initialization failed: no valid executable found for OCI runtime crun: invalid argument
DEBU[0000] configured OCI runtime kata initialization failed: no valid executable found for OCI runtime kata: invalid argument
DEBU[0000] configured OCI runtime runsc initialization failed: no valid executable found for OCI runtime runsc: invalid argument
DEBU[0000] Using OCI runtime "/usr/bin/runc"
INFO[0000] Found CNI network podman (type=bridge) at /etc/cni/net.d/87-podman.conflist
DEBU[0000] Default CNI network name podman is unchangeable
INFO[0000] Setting parallel job count to 13
DEBU[0000] Strongconnecting node 3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df
DEBU[0000] Pushed 3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df onto stack
DEBU[0000] Finishing node 3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df. Popped 3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df off stack
DEBU[0000] Made network namespace at /run/netns/cni-88ad0b5e-48fc-1963-f99a-0f46020d6eee for container 3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df
INFO[0000] Got pod network &{Name:quay-pod Namespace:quay-pod ID:3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df NetNS:/run/netns/cni-88ad0b5e-48fc-1963-f99a-0f46020d6eee Networks:[{Name:podman Ifname:eth0}] RuntimeConfig:map[podman:{IP: MAC: PortMappings:[{HostPort:8443 ContainerPort:8443 Protocol:tcp HostIP:}] Bandwidth:<nil> IpRanges:[]}] Aliases:map[]}
INFO[0000] Adding pod quay-pod_quay-pod to CNI network "podman" (type=bridge)
DEBU[0000] [0] CNI result: &{0.4.0 [{Name:cni-podman0 Mac:ae:03:61:f5:03:53 Sandbox:} {Name:veth0359a897 Mac:7e:8a:a4:c0:98:6e Sandbox:} {Name:eth0 Mac:66:d9:b8:db:84:5e Sandbox:/run/netns/cni-88ad0b5e-48fc-1963-f99a-0f46020d6eee}] [{Version:4 Interface:0xc0003d0908 Address:{IP:10.88.56.53 Mask:ffff0000} Gateway:10.88.0.1}] [{Dst:{IP:0.0.0.0 Mask:00000000} GW:<nil>}] {[]  [] []}}
DEBU[0000] Tearing down network namespace at /run/netns/cni-88ad0b5e-48fc-1963-f99a-0f46020d6eee for container 3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df
INFO[0000] Got pod network &{Name:599d48df4d81-infra Namespace:599d48df4d81-infra ID:3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df NetNS:/run/netns/cni-88ad0b5e-48fc-1963-f99a-0f46020d6eee Networks:[{Name:podman Ifname:eth0}] RuntimeConfig:map[podman:{IP: MAC: PortMappings:[{HostPort:8443 ContainerPort:8443 Protocol:tcp HostIP:}] Bandwidth:<nil> IpRanges:[]}] Aliases:map[]}
INFO[0000] Deleting pod 599d48df4d81-infra_599d48df4d81-infra from CNI network "podman" (type=bridge)
DEBU[0000] Cleaning up container 3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df
DEBU[0000] Network is already cleaned up, skipping...
DEBU[0000] Container 3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df storage is already unmounted, skipping...
Error: error starting container 3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df: failed to mount shm tmpfs "/var/lib/containers/storage/overlay-containers/3fa67abdaed25e3c4c2c128ba81a9474ae8d6b07efab4d81dee9b2e2862f50df/userdata/shm": invalid argument
DA

Responses