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.

Sign up for GitHub

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

Jump to bottom

Add ability to load libpod default configuration from file #270

Closed
mheon opened this issue Jan 29, 2018 · 5 comments
Closed

Add ability to load libpod default configuration from file #270

mheon opened this issue Jan 29, 2018 · 5 comments
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@mheon
Copy link
Member

mheon commented Jan 29, 2018

Similar to c/image and c/storage, libpod should load its default configuration in from a file, to allow unified system-wide container runtime settings to be honored by default
@surajssd
Copy link
Contributor

surajssd commented Feb 6, 2018

@mheon how are these configs fed right now?

@mheon
Copy link
Member Author

mheon commented Feb 6, 2018

Right now we respect the default containers/storage and containers/image configs. The storage config lives at /etc/containers/storage.conf (I'm not entirely sure where the image configs reside, never needed to tweak them). Changes to storage.conf will affect all users of containers/storage on the system (libpod, CRI-O, etc) unless they are explicitly set to ignore them via command line flag.

@rhatdan
Copy link
Member

rhatdan commented Feb 6, 2018

/etc/containers/registries,conf /etc/containers/policy.json /etc/containers/registries.d are all used in containers/image.

@mheon
Copy link
Member Author

mheon commented Mar 4, 2018

Will be fixed by #430

@mheon
Copy link
Member Author

mheon commented Mar 15, 2018

Support was merged

@mheon mheon closed this as completed Mar 15, 2018
@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 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rhatdan @surajssd @mheon