Skip to content

Podman 'Failed to obtain podman configuration: runroot must be set' (missing a configuration key in storage.conf) #219821

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

Open
4 tasks done
hwalinga opened this issue Apr 12, 2025 · 0 comments

Comments

@hwalinga
Copy link

brew gist-logs <formula> link OR brew config AND brew doctor output

https://gist.github.com/hwalinga/92f97b3b670b79f4f2cf43c87d21e746

Verification

  • My brew doctor output says Your system is ready to brew. and am still able to reproduce my issue.
  • I ran brew update and am still able to reproduce my issue.
  • I have resolved all warnings from brew doctor and that did not fix my problem.
  • I searched for recent similar issues at https://github.com/Homebrew/homebrew-core/issues?q=is%3Aissue and found no duplicates.

What were you trying to do (and why)?

# podman info
Failed to obtain podman configuration: runroot must be set

What happened (include all command output)?

The podman install provides an invalid storage.conf (

(prefix/"etc/containers/storage.conf").write <<~EOS
) missing the runroot key. See containers/podman#25268

If the storage.conf is not available it defaults to /run/user/1000/containers/, so perhaps setting this to /home/linuxbrew/.linuxbrew/var/run/user/1000/containers?

What did you expect to happen?

I want podman to just works with valid configuration out of the box, without figuring out what configuration needs to change.

Step-by-step reproduction instructions (by running brew commands)

brew install podman
podman info
# Failed to obtain podman configuration: runroot must be set
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant