-
Notifications
You must be signed in to change notification settings - Fork 203
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
Remove libpod.conf #369
Remove libpod.conf #369
Conversation
We no longer support libpod.conf, remove any code that deals with it. Signed-off-by: Daniel J Walsh <[email protected]>
@containers/podman-maintainers PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Ciao libpod.conf!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhatdan, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
I've got to write a "varlink is dead" note, I'll add libpod.conf to that. Is there anything a user who has a highly customized libpod.conf should do to migrate to containers.conf? They can simply rename/move the file to containers.conf if they want to right? |
No - structure is sufficiently different to prevent that - but almost all the settings do have the same names as they did before. |
firewall types: remove unnecessary clones
We no longer support libpod.conf, remove any code that deals with it.
Signed-off-by: Daniel J Walsh [email protected]