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
Can't set graphRoot and runRoot via configuration #18375
Comments
Did you run |
i tried doing so, but it still points to the same storages
why does it want me to remove storage.conf that i've created specifically? |
Found more info: changing graphroot and runroot on default user installation (that is, |
i think i might have found answer for this #10762 (comment) So when i set rootless_storage_path it changed graphRoot accordingly... didn't change runRoot though (is that an issue? would containers clash with eachother that way if they are the same name in different configurations?) |
A friendly reminder that this issue had no activity for 30 days. |
@Meister1593 Interested in opening a PR to fix Documentation? |
Looks like I have this issue too. I had a user that is 1000, added one that I use all the time, which is 1001. However, podman ignores the fact that I have the only config (I've checked all three possible locations) at /etc/containers/ and also ignores its contents. No matter what It baffles me so much I just create a symlink on every startup with a script, but surely this isn't the solution? Edit: after a few resets, migrations and reboots, podman now correctly understands the location. |
Issue Description
Hello. I'm currently developing completely portable rootless distrobox/podman installation for using ALVR under Linux and have discovered some issues with setting configuration for storage.conf.
So to make it completely portable (so that it never interferes with other configurations) i need to override pretty much every single configuration that is related to containers, volumes, etc etc, and that includes graphRoot and runRoot.
When i tried doing so, it still pointed at home folder and same xdg runtime directory.
Steps to reproduce the issue
Steps to reproduce the issue
podman info
Describe the results you received
Graphroot and runroot points to same location
Describe the results you expected
Graphroot and runroot should point to location i've specified in storage.conf
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Running on Fedora Silverblue 38, installing podman using this script
Additional information
storage.conf
The text was updated successfully, but these errors were encountered: