-
Notifications
You must be signed in to change notification settings - Fork 68
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: set appropriate defaults for interval
, timeout
and retries
#225
Conversation
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]>
@flouthoc: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The new test Dockerfile should also be added to the |
Test: []string{"CMD-SHELL", "/app/check.sh --quiet"}, | ||
}, | ||
}, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm probably overthinking, but I just wonder if we're starting to brush up against DockerHub rate limits. No need to adjust, just thought I'd put that thought out there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We tend to use one of a handful of base images for various tests, and the docker daemon hangs on to them between tests, but you're not wrong to be concerned that it will become a problem at some point.
LGTM, once @nalind 's concerns are addressed. |
It is documented here https://docs.docker.com/engine/reference/builder/#healthcheck that I have also verified this against conformance tests so this PR must not go in and alt is: containers/podman#13928 |
Set appropriate defaults for
--interval
,--timeout
and--retries
whenprocessing a Containerfile with build format as docker.
See: https://docs.docker.com/engine/reference/builder/#healthcheck
Closes: containers/podman#13912