-
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
healthcheck never executes when Dockerfile lacks --interval #13912
Comments
Set appropriate defaults from interval, timeout and retries when processing a Containerfile with build format as docker. See: https://docs.docker.com/engine/reference/builder/#healthcheck Closes: containers/podman#13912 Signed-off-by: Aditya R <[email protected]>
Hi @nvllsvm , Thanks for creating the issue this is something which i think must be fixed at imagebuilder so this will be fixed by openshift/imagebuilder#225 |
@flouthoc Is that PR specific to |
@nvllsvm I have verified your use-case where the image is built with |
@nvllsvm Above PR should close it. I don't know why it is documented here as |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
This image has a healthcheck which touches a file in
/healthchecks
each execution. The filename is the current epoch time so files should accumulate overtime.Dockerfile
containing:cd
to the new directory and runpodman build . -t dev --format docker
podman run -d --name test --rm dev
podman ps
and notice that theSTATUS
is stillstarting
.podman exec test ls /healthchecks
and notice there are no files.Describe the results you expected:
Since the
Dockerfile
lacks an explicit--interval
for the healthcheck, I expect the healthcheck to execute every 30 seconds per the default mentioned at https://docs.docker.com/engine/reference/builder/#healthcheck .Additional information you deem important (e.g. issue happens only occasionally):
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)
Yes - I have also replicated this on Arch Linux running a build of master commit d6f47e6
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: