-
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
Docker Compose health check disable flag is not handled correctly #14493
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
I'll take this one |
@jakecorrenti Can you take this one? I'm not going to find time this week |
Sure thing, I can take a look |
jakecorrenti
pushed a commit
to jakecorrenti/podman
that referenced
this issue
Jun 17, 2022
Previously, if a container had healthchecks disabled in the docker-compose.yml file and the user did a `podman inspect <container>`, they would have an incorrect output: ``` "Healthcheck":{ "Test":[ "CMD-SHELL", "NONE" ], "Interval":30000000000, "Timeout":30000000000, "Retries":3 } ``` After a quick change, the correct output is now the result: ``` "Healthcheck":{ "Test":[ "NONE" ] } ``` Additionally, I extracted the hard-coded strings that were used for comparisons into constants in `libpod/define` to prevent a similar issue from recurring. Closes: containers#14493 Signed-off-by: Jake Correnti <[email protected]>
jakecorrenti
pushed a commit
to jakecorrenti/podman
that referenced
this issue
Jul 5, 2022
Previously, if a container had healthchecks disabled in the docker-compose.yml file and the user did a `podman inspect <container>`, they would have an incorrect output: ``` "Healthcheck":{ "Test":[ "CMD-SHELL", "NONE" ], "Interval":30000000000, "Timeout":30000000000, "Retries":3 } ``` After a quick change, the correct output is now the result: ``` "Healthcheck":{ "Test":[ "NONE" ] } ``` Additionally, I extracted the hard-coded strings that were used for comparisons into constants in `libpod/define` to prevent a similar issue from recurring. Closes: containers#14493 Signed-off-by: Jake Correnti <[email protected]>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 20, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Podman seems to ignore the
healthcheck
disable flag set via Docker Compose.Steps to reproduce the issue:
Setup Podman service (to emulate a Docker socket).
Create a Docker Compose service for a container that has healthchecks defined and then disable them using
healthcheck
(example):Describe the results you received:
Health checks are not disabled properly. Inspecting the container (for example:
podman inspect dashy
):If we remove the
healthcheck
section from the service definition, we see the default healthcheck, as expected:Describe the results you expected:
When we run the same container directly using the Podman CLI and pass in
--no-healthcheck
, we get the desired behavior:The Docker Compose
healthcheck
disable flag should be handled the same way.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 - also tested with a version built manually:
Additional environment details (AWS, VirtualBox, physical, etc.):
Running in KVM on Proxmox.
The text was updated successfully, but these errors were encountered: