-
Notifications
You must be signed in to change notification settings - Fork 489
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
Support healthcheck associative array #22
Support healthcheck associative array #22
Conversation
I needed to add |
Thank you very much for this kind contribution. I'll look into it very soon |
Hmm, looks like |
there are two things here
build-time issues should be reported to buildah from the compose.yml reference
which should be interpreted as
assuming default shell this means that podman should interpret https://docs.docker.com/compose/compose-file/#healthcheck |
I've seen the diff, it's not no worries, I'll fixes it ASAP. |
Map keys to corresponding --healthcheck-XXX option Unfortunately --healthcheck-command only accepts a string, not a list of strings. Furthermore it splits the string on whitespace. Therefore the mapping of all allowed Docker Compose values is not possible.
695a303
to
6b3e708
Compare
Unfortunately things aren't that easy. It turns out that
ends up in the container configuration as "Healthcheck": {
"Test": [
"stat",
"/etc/passwd",
"||",
"exit",
"1"
], My updated patch tries to approximate as best as possible, but not all valid Docker Compose values will be able to be mapped correctly |
I've used
|
Map keys to corresponding --healthcheck-XXX option