-
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
--timestamp does nothing if only instruction is from #15171
Comments
Hi @graywolf-at-work , Thanks for creating the issue. I think that is expected since existing image is retagged and no new image is created. |
I will make a PR documenting this then. Thanks for explaining :) |
I assume the man pages are build from the markdown I've edited in the PR. Is the correct or are other changes required as well? |
Does this work for you. |
Yes, that does seem to work, thank you. However, sadly I'm limited to using podman. |
We should add the --timestamp option to Podman commit. Which would satisfy your needs. |
Fixes: containers#15171 Signed-off-by: Tomas Volf <[email protected]>
Fixes: containers#15171 Signed-off-by: Tomas Volf <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When you have a Containerfile that has only
from
instruction, the --timestampoption for
podman build
does nothing.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):
N/A
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/main/troubleshooting.md)
No
Additional environment details (AWS, VirtualBox, physical, etc.):
N/A
The text was updated successfully, but these errors were encountered: