-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
containers.conf -> infra_image doesn't work #12245
Comments
Thanks for reaching out, I'll prepare a fix. |
otherwise the setting in the containers.conf file is not honored. Closes: containers#12245 Signed-off-by: Giuseppe Scrivano <[email protected]>
opened a PR: #12249 |
@vrothberg ah sorry, I was working on that already, does the fix LGTY? |
LGTM |
Fix a bug where pods would be created with the hard-coded default infra image instead of the custom one from containers.conf. Add a simple regression test. Fixes: containers#12245 Signed-off-by: Valentin Rothberg <[email protected]>
Hello, has this been released in the |
I doubt it, most likely will not be released until Podman 4.0 |
This bug is actually boring because when we configure the infra image in containers.conf it's not taken into account :/ |
You could always attempt to setup a mirror for the image. |
/kind bug
Description
Cannot change infra_image by using user containers.conf
Steps to reproduce the issue:
Edit file
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
It still doesn't work after modifying
/usr/share/containers/containers.conf
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
physical/Fedora35
The text was updated successfully, but these errors were encountered: