rootless podman ERRO[0000] error joining network namespace for container #6800
Comments
openshift-ci-robot
added
the
kind/bug
|
This is most likely systemd killing Podman and removing the login session for the user in question. You need to run Also, we strongly recommend you use |
|
thanks for your response @mheon Also the container auto start is not consistent if I do the reboot again. |
|
Hi @mheon I updated my podman run scripts to run as pod . and generated systemd unit file for pod . But still no success
|
|
can someone help me to resolve the above mentioned issue. |
|
If that |
|
I executed this command as podman user only |
|
In my case, this was an SELinux Issue. Try to create your container with
check your user environment especially $XDG_RUNTIME_DIR. The easiest way to fix this is to login directly as user "podman" or try for further information about this issue take a look at |
|
A friendly reminder that this issue had no activity for 30 days. |
|
Is this still an issue? |
Sorry for the delay. Our platform team updated the podman installation recently. I am yet to verify it. Soon I will test and post my updates here. |
|
Any podman command I run, gives:
ERRO[0000] error joining network namespace for container 470b76724bcff05db55806baeb376b9951e8a4db66412937ed827e3d18677e4a: error retrieving network namespace at /run/user/1000/netns/cni-8bf84c49-dcbd-bd4b-f954-a09d142834f0: failed to Statfs "/run/user/1000/netns/cni-8bf84c49-dcbd-bd4b-f954-a09d142834f0": no such file or directory ERRO[0000] unable to get container info: "container 470b76724bcff05db55806baeb376b9951e8a4db66412937ed827e3d18677e4a is not valid: container has already been removed" I have stopped and removed all containers, and run podman system prune --all |
|
Does |
|
Yes, it appears to. |
|
Seems to be fixed, closing - please re-open if incorrect |
|
Getting Similar error |
|
@mheon could you please reopen this issue. |
|
I'd recommend opening a new issue - this one has gotten very stale. |
|
WSL2 / Alpine:edge / podman version 3.1.0 How to resolve? |
|
podman 3.1.1 Should resolve this, but has not been released yet. You are best to roll back to previous version 3.1.1 should be released early next week. Or build the package from the upstream. |
|
For rootless podman users on WSL2: as far as I can tell this happens after a reboot because podman needs to refresh its state after a reboot, but was unable to detect that the system has rebooted in WSL2. Solution: Useful info about this in https://www.redhat.com/sysadmin/sudo-rootless-podman. |
|
Since WSL2 does not have systemd or mount /tmp with tmpfs, then it breaks the assumption. Do you know if there is a similar way to trigger this behaviour in WSL2? IE Cause certain files to be deleted? Do we need to drop an init script? |
|
My understanding is there is no systemd/init.d at all; it seems we can run things at startup via the Windows scheduler (example) but that's not very convenient. In my case I made do with assuming that function refresh_rootless_podman_after_reboot {
local libpod_tmp="/tmp/run-$(id -u)/libpod/tmp"
if [ /proc/1 -nt "${libpod_tmp}" ]; then
rm -rf "${libpod_tmp}"
fi
}
refresh_rootless_podman_after_rebootBut a simpler solution could be to include the boot ID in the temp path so we always get a fresh folder after reboot, e.g |
|
@alexcern by anychance, is the folder change in 3.3.4, or it's depend on the distro? because the folder changed to /tmp/podman-run-(uid)/ |
|
The below command worked for me (running Podman 3.4.2 on WSL 2):
|
|
I just encountered this issue with podman 4.0.2 on AlmaLinux 8, no WSL. The containers were created by testcontainers over the Podman socket, not sure if that did anything special. |
|
Could you update to podman 4.1 and see if this continues to happen. Please open a new issue rather then adding to a closed issue. |
|
Hi, We are using podman 4.1.1 We are using Ansible Automation Platform, which relies on podman and I am still seeing the issue. I do not see any directory What is the impact of this error? Can it reduce production in our platform? So far, the errors are there but I do not think they are impacting our workloads. |
|
@rhatdan Getting this issue with RHEL9 and podman 4.0.2, is there any update/fix/workaround? |
|
Did you enable the linger? |
|
@rhatdan Do you mean |
|
Yes |
|
@rhatdan I'll try it out, thanks |
|
@rhatdan, on my system (Rocky Linux 9.1 with Podman 4.2.0) this is still an issue. Lingering is enabled but containers are not started and the same error as described in this issue pops up: [podman@server2 ~]$ loginctl user-status $(id -un)
podman (990)
Since: Sat 2023-01-14 16:37:06 CET; 31s ago
State: lingering
Linger: yes
Unit: user-990.slice
└─[email protected]
└─init.scope
├─844 /usr/lib/systemd/systemd --user
└─846 "(sd-pam)"
[podman@server2 ~]$ podman ps
ERRO[0000] Joining network namespace for container 2c01eddb8ae6b41f455fb2e71885760b886073cfcd684080285d7032b87c6f64: error retrieving network namespace at /run/user/990/netns/netns-5c8ceec4-2678-8a95-a179-6a06aa4f56db: failed to Statfs "/run/user/990/netns/netns-5c8ceec4-2678-8a95-a179-6a06aa4f56db": no such file or directory
ERRO[0000] Joining network namespace for container 350ea594aa7ddc839c9c6dd2409af8b02ce9b5ee66d51f15220d5d28acce993f: error retrieving network namespace at /run/user/990/netns/netns-2b1876a9-f55d-cd66-5caf-ac131fa5f7a6: failed to Statfs "/run/user/990/netns/netns-2b1876a9-f55d-cd66-5caf-ac131fa5f7a6": no such file or directory
ERRO[0000] Joining network namespace for container 67476af881d80ba69cc5dd986895a51e903df155a7a721258de8a1713c3fffa3: error retrieving network namespace at /run/user/990/netns/netns-59834835-a5bd-9ce4-149b-e5d39aeb1f6a: failed to Statfs "/run/user/990/netns/netns-59834835-a5bd-9ce4-149b-e5d39aeb1f6a": no such file or directory
ERRO[0000] Joining network namespace for container 72a55ef327eef91e9aed97c9ece53cda4b2d2e4b14a522a458090d0cf7eff6d9: error retrieving network namespace at /run/user/990/netns/netns-aa5a8b18-af6e-66ce-fa01-33140ae534d6: failed to Statfs "/run/user/990/netns/netns-aa5a8b18-af6e-66ce-fa01-33140ae534d6": no such file or directory
ERRO[0000] Joining network namespace for container 79f863de695267f3027d835b4f78e7e418a23b8feeae14fd2889e833a60a1aa8: error retrieving network namespace at /run/user/990/netns/netns-05f00422-064f-49c7-0875-10f81401bf31: failed to Statfs "/run/user/990/netns/netns-05f00422-064f-49c7-0875-10f81401bf31": no such file or directory
ERRO[0000] Joining network namespace for container 7d7a707ee255e4b04e13cd617d0b09d44dcd2d7aaf20a19d888392843ecdc67e: error retrieving network namespace at /run/user/990/netns/netns-b668c156-48f4-abdf-21ac-901206352a62: failed to Statfs "/run/user/990/netns/netns-b668c156-48f4-abdf-21ac-901206352a62": no such file or directory
ERRO[0000] Joining network namespace for container 7e75f6b8b1d6e9fde848c43fde7bbade2330f7a6a44d52e1ae988e316045a13a: error retrieving network namespace at /run/user/990/netns/netns-022fff9c-6e50-785f-461b-bfb625952317: failed to Statfs "/run/user/990/netns/netns-022fff9c-6e50-785f-461b-bfb625952317": no such file or directory
ERRO[0000] Joining network namespace for container 883568b6d14f81577ae34ea12fd38be28d1b8580ab355b6baf8621d4be2bb469: error retrieving network namespace at /run/user/990/netns/netns-73bae70b-6ac0-d546-22fe-44d261e45267: failed to Statfs "/run/user/990/netns/netns-73bae70b-6ac0-d546-22fe-44d261e45267": no such file or directory
ERRO[0000] Joining network namespace for container b72a579b0868c014760cd76bfc8d52c35495bc35c2d171cac42a28508e89bd0a: error retrieving network namespace at /run/user/990/netns/netns-66d1bf2f-b8a1-61e8-345e-2bac9f4f8007: failed to Statfs "/run/user/990/netns/netns-66d1bf2f-b8a1-61e8-345e-2bac9f4f8007": no such file or directory
ERRO[0000] Joining network namespace for container cc67ed6bc5cc3209d39b1d41234a2675d355442cd136d5e11727734b10b24bcf: error retrieving network namespace at /run/user/990/netns/netns-9b83d2a4-c5b7-e681-b6ea-0e3208e60e3d: failed to Statfs "/run/user/990/netns/netns-9b83d2a4-c5b7-e681-b6ea-0e3208e60e3d": no such file or directory
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESI started a whole bunch of containers using docker-compose and Any ideas? |
|
Do you have podman-restart enabled? |
No, I did not have it enabled (was not aware of it). Enabling the service and rebooting the |
github-actions
bot
added
the
locked - please file new issue/PR
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
To manage containers after the system reboot I am trying setup systemd script for rootless podman containers.
podman run command
cat /etc/systemd/system/paperkraft.serviceSteps to reproduce the issue:
Run the container
systemctl daemon-reload
systemctl enable paperkraft.service
Created symlink from /etc/systemd/system/multi-user.target.wants/paperkraft.service to /etc/systemd/system/paperkraft.service.
Describe the results you received:
After the system reboot container are not started and giving the below output for
podman psorpodman ps -aDescribe the results you expected:
paperkraft container should be running state
Additional information you deem important (e.g. issue happens only occasionally):
System reboot
Output of
podman version:Output of
podman info --debug:Package info (e.g. output of
rpm -q podmanorapt list podman):Additional environment details (AWS, VirtualBox, physical, etc.):
AWS & VM
The text was updated successfully, but these errors were encountered: