-
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
podman pod create
command ignored the default pod infra image specified in containers.conf
#12771
Comments
This is working for me on podman 3.4?
|
|
But that's not the issue.
Issue: podman ignores the configuration of infra_image in the configuration files |
Yes I set this default in my ~/.config/containers/containers.conf
|
OK but I still get this result
Only
|
Same issue on the MacBook Pro M1 and additionally the command
|
podman pod create
command ignored the default pod infra image specified in containers.conf
Remove hard code use of the DefaultInfraImage and rely on getting this from containers.conf. Fixes: containers#12771 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Is this fixed? |
Yes and No! tested with pre-release 4.0.0-RC2 ==> No / not ok
==> Yes / ok
|
Your failure case is actually another 4.0 change - the default is now to not pull the infra image, but to build one locally based on a local pause binary - so the localhost image is the one we built. This improves Podman's ability to work on systems without an internet connection. |
Yes, I am aware of that. But why does the command no default configuration of infra_image in any containers.conf
expected output for example: ... (default "localhost/podman-pause:4.0.0-rc2-1642795764") default configuration of infra_image set in local containers.conf
output as expected: ... (default "registry.access.redhat.com/ubi8/pause") By the way, the solution is fine for me, the small output error does not bother me. |
@rhatdan Looks like a bug? |
Possibly only a small fix needed in pkg
Example change to
|
Please open a PR? |
|
Hi, is there any chance, this fix is going to be backported to 3.4.2-rhel? This is a major breakage for us on rhel 8.5. |
The fixes will make it into RHEL 8.6 and according to https://bugzilla.redhat.com/show_bug.cgi?id=2055313 there is fair chance also to 8.5. Note that RHEL-related questions should go through the Red Hat channels (e.g., Bugzilla). This will make sure that the issues receive the right priority and attention. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman pod create
command ignored the default pod infra image specified in containers.confalso the commands
podman create --pod new:
podman run --pod new:
issue exist on CentOS Stream 9 with podman 3.4.3-dev and Red Hat Enterprise Linux 9.0 Beta (Plow) with podman 4.0.0-dev
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:CentOS Stream 9
Enterprise Linux 9.0 Beta (Plow)
Output of
podman info --debug
:CentOS Stream 9
Enterprise Linux 9.0 Beta (Plow)
Package info (e.g. output of
rpm -q podman
orapt list podman
):CentOS Stream 9
Enterprise Linux 9.0 Beta (Plow)
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.):
VMware Fusion
The text was updated successfully, but these errors were encountered: