Bug 1222663 - Containers not able to start
Summary: Containers not able to start
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Containers (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Containers Team
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-11 08:17 UTC by Samuel Conway
Modified: 2024-04-12 08:06 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Samuel Conway 2024-04-11 08:17:08 UTC 
related to https://github.com/containers/podman/issues/22168#issuecomment-2049072614

I updated my openSUSE MicroOS server to version 20240409, but still getting error:
`Error: starting container xxx: rootless netns: mount resolv.conf to "/run/user/1000/containers/networks/rootless-netns/run/netconfig/resolv.conf": no such file or directory`

This was supposedly fixed in Tumbleweed snapshot 20240409.

I understood MicroOS and Tumbleweed used the same package versions?

Kind regards,
Sam
Comment 1 Samuel Conway 2024-04-12 08:05:28 UTC 
solved by running: podman unshare --rootless-netns true then re-creating pods
Comment 2 Samuel Conway 2024-04-12 08:06:05 UTC 
may be closed