-
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 build behaves differently from docker build #7398
Comments
@TomSweeneyRedHat PTAL |
@c-goes on a quick look, I'm not sure why Podman isn't acting like Docker in this instance. FWIW, after Docker completes, it sets the time zone to UTC +0000 (blank), which you probably don't want:
In the short term, if you want to emulate that, you can add this ARG line to your Dockerfile after your ENV statement:
or better yet, also add a ENV for the TZ variable to your Dockerfile too:
Which will give you:
I'll try to figure out what's going on in the mean time, but this will be at a lower priority as there's the above workaround. Hope that helps. |
@TomSweeneyRedHat, can we move it over to buildah? |
I think this one lives in both Buildah and Podman, but if you want to move it, feel free. Personally I'm wondering if it's something we should fix or not. I'm not convinced that what Docker is doing is correct in this instance, but just setting the UTC to zero if unset might be the way to go to avoid the TZ ask for a script. |
Is the difference that Docker does not provide a tty to ask the question at, and podman/Buildah does? Apt figures there is no tty so it just continues the install? |
@rhatdan, the tty/notty angle sounds like a very good theory. |
If you run the podman build command with < /dev/null, does this fix the situation? |
@c-goes Are you still having this issue? |
Works for me now. Thank you. |
I'm sorry, I was wrong. It doesn't work, tested with master branch. |
A friendly reminder that this issue had no activity for 30 days. |
This should be fixed in main branch, since I know the stdin is disabled, I am working on a mechanism to add a flag for people who want this ability back under certain circumstances. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I tried building this image (https://github.com/geerlingguy/docker-ubuntu2004-ansible) with Podman and found out that Docker behaves differently from Podman. While Docker builds the image successfully, Podman stops and asks for geographic area (related issue: geerlingguy/docker-ubuntu2004-ansible#2 (comment)).
Steps to reproduce the issue:
Clone https://github.com/geerlingguy/docker-ubuntu2004-ansible
run
podman build -t ubuntu2004-ansible .
Describe the results you received:
(at this point the build stops)
Describe the results you expected:
For best Docker compatibility the output should be similar to Docker:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
: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?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
physical
The text was updated successfully, but these errors were encountered: