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

Wrong user id on Debian #18633

Closed
Mte90 opened this issue May 19, 2023 · 8 comments
Closed

Wrong user id on Debian #18633

Mte90 opened this issue May 19, 2023 · 8 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

@Mte90
Copy link

Mte90 commented May 19, 2023

Issue Description

I have an old workstation that I am still using with debian sid since 10 years.

So I had some issue on running podman for missing setuid/setgid that was missing and I added them. I changed the id from 1000 to 10000 because there was some issues.
I am able only to run on root, if I run from the user I get this:

immagine

If you need more commands to run let me know.

Steps to reproduce the issue

The screen above

Describe the results you received

An error

Describe the results you expected

Don't get any error...

podman info output

Debian sid, podman 4.3.1+ds1-8

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

@Mte90 Mte90 added the kind/bug Categorizes issue or PR as related to a bug. label May 19, 2023
@Luap99
Copy link
Member

Luap99 commented May 19, 2023

Switching the UID is not supported by podman as we store full paths in our db. #11377

Something like rm -rf ~/.local/share/containers/storage/ should remove all podman data and get it back working after that.

@Luap99 Luap99 closed this as completed May 19, 2023
@Mte90
Copy link
Author

Mte90 commented May 19, 2023

Doesn't fix that command the issue I have.
I replied on that ticket 3 weeks ago for the same issue.

The folder on /home/mte90/.local/share/containers/ is empty.

@Luap99
Copy link
Member

Luap99 commented May 19, 2023

Do you have a containers.conf or storage.conf that defines this incorrect path?

@Luap99
Copy link
Member

Luap99 commented May 19, 2023

Is XDG_RUNTIME_DIR set properly?

@Mte90
Copy link
Author

Mte90 commented May 19, 2023

$XDG_RUNTIME_DIR = /tmp/runtime-mte90

About containers.conf I don't find that file, there isn't anything on /etc/containers/storage.conf.

@Mte90
Copy link
Author

Mte90 commented May 22, 2023

Any hint where is getting this value?
I am checking the code but I don't find anything.

@Luap99
Copy link
Member

Luap99 commented May 22, 2023

try running podman --log-level debug ...

@Mte90
Copy link
Author

Mte90 commented May 22, 2023

Bingo!

I mapped the folder for podman stuff in a different folder so in my case the database it was on /media/mte90/Doh-cker/junk/rootless-storage/libpod/bolt_state.db. Removed that file and now is working as non root.

Just for someone looking for the same command podman --log-level debug info

@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 Aug 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 23, 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

2 participants