Skip to content
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

Inspect field .State.Health vs. .State.Healthcheck #13720

Closed
white-gecko opened this issue Mar 30, 2022 · 4 comments
Closed

Inspect field .State.Health vs. .State.Healthcheck #13720

white-gecko opened this issue Mar 30, 2022 · 4 comments
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

@white-gecko
Copy link

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

In a script (currently for docker) with a command:

docker inspect --format='{{json .State.Health.Status}}' container_name

however, for podman the field is called Healthcheck

docker inspect --format='{{json .State.Healthcheck.Status}}'

To reach better convergence, I suggest to provide an alias for that.

Steps to reproduce the issue:

  1. Get the output of docker inspect and podman inspect
  2. Look for the field Health resp. Healthcheck

Describe the results you received:
For docker I can find .State.Health.Status
For podman I can find .State.Healthcheck.Status

Describe the results you expected:
I expect convergence to docker output, if this is possible

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Version:      3.4.4
API Version:  3.4.4
Go Version:   go1.16.8
Built:        Wed Dec  8 22:45:07 2021
OS/Arch:      linux/amd64

Output of podman info --debug:

(paste your output here)

Package info (e.g. output of rpm -q podman or apt list podman):

podman-3.4.4-1.fc35.x86_64

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.):
local laptop

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 30, 2022
@mheon
Copy link
Member

mheon commented Mar 30, 2022

@flouthoc Mind taking this one?

@Luap99
Copy link
Member

Luap99 commented Mar 30, 2022

I am almost sure I fixed this at some point.

@white-gecko
Copy link
Author

Sorry, I couldn't verify this with the latest version. So maybe you should verify it first :-\

@Luap99
Copy link
Member

Luap99 commented Mar 30, 2022

#11654, this is fixed in 4.0

@Luap99 Luap99 closed this as completed Mar 30, 2022
@github-actions 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
@github-actions github-actions bot locked as resolved and limited conversation to collaborators 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.
Projects
None yet
Development

No branches or pull requests

3 participants