-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman list fails in rawhide #2935
Comments
@giuseppe PTAL |
this is probably caused by the recent change of using only one namespace. @matthiasclasen how many containers for the user are running? I think it is required to stop them first, and then restarting them will ensure they are in the same user namespace |
none are running. this is after rebooting into a new silverblue image |
Can you please show the output for: |
|
so the issue we are hitting here was fixed by 6c6a865, unfortunately the fix doesn't work for containers that were created without the fix. I wonder if we can add a command like "system rootless-restore" that stops all the containers, changes the configuration for the conmon pid file to be in the static directory and then restart the containers. Matt, would it be ok? What about changing the configuration? |
I don't know anything about podman configuration. You will have to tell me what I need to change. |
sorry, the "Matt" was for @mheon :-) |
Hm. We have the core mechanism to do that from @giuseppe I'd call the command |
But no fundamental objection to adding a command that will migrate container configurations to change things like this, as long as we guarantee the containers are down when we make the changes. |
opened a PR here: #2950 I've currently marked it as WIP as I'll continue working on it |
it is useful to migrate existing containers to a new version of podman. Currently, it is needed to migrate rootless containers that were created with podman <= 1.2 to a newer version which requires all containers to be running in the same user namespace. Closes: containers#2935 Signed-off-by: Giuseppe Scrivano <[email protected]>
This was triggered by changes to rootless Podman containers in podman-1.3.0 [1]. Containers created with version 1.2.0 or older need to be migrated. [1] containers/podman#2935
This was triggered by changes to rootless Podman containers in podman-1.3.0 [1]. Containers created with version 1.2.0 or older need to be migrated. [1] containers/podman#2935 https://github.com/debarshiray/toolbox/pull/166
The text was updated successfully, but these errors were encountered: