Skip to content
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

system reset doesn't work after user has been recreated #9413

Closed
quantum77 opened this issue Feb 17, 2021 · 7 comments
Closed

system reset doesn't work after user has been recreated #9413

quantum77 opened this issue Feb 17, 2021 · 7 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@quantum77
Copy link

/kind bug

Description
When creating a new user and deleting an old user podman no longer works.
$ podman images
Error: error creating tmpdir: mkdir /run/user/1000: permission denied

$ podman system reset
Error: error creating tmpdir: mkdir /run/user/1000: permission denied

What does resolve the error:
$ rm -rf ~/.local/share/containers

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Feb 17, 2021
@mheon
Copy link
Member

mheon commented Feb 17, 2021

Core of the issue seems to be that system reset requires Podman to successfully create the libpod Runtime before system reset will run. If you encounter an issue where the runtime cannot be created, e.g. a path issue like this, podman system reset cannot run, so the user can't reset their storage and fix the bug.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Mar 23, 2021

This looks like XDG_RUNTIME_DIR was not set correctly. How do you get into this condition?

@mheon
Copy link
Member

mheon commented Mar 23, 2021

@rhatdan The paths cached in the database no longer match system configuration. XDG_RUNTIME_DIR does not come into this.

The solution will require a significant rewrite to system reset, which will have to be rewritten to be part of runtime init so we can avoid errors of this type.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@vrothberg
Copy link
Member

How do you get into this condition?

I wonder as well.

@vrothberg vrothberg changed the title $ podman system reset - Catch 22 system reset doesn't work after user has been recreated Dec 13, 2021
@vrothberg
Copy link
Member

Closing in favor of #11377 which has some reproducer

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

5 participants