You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a healthcheck can only be added to a container when building it. Existing of-the-shelve containers that are not supposed to be modified cannot be run with a healthcheck if not included by upstream image vendor. Defining healthchecks in / from Docker Compose files is not supported.
Info
docker-maven-plugin version : 0.43.4
Maven version (mvn -v) : 3.9.1
Docker version : Moby 25.0.0-beta.1, build 2b521e4
If it's a bug, how to reproduce : Not a bug
If it's a feature request, what is your use case : Add healthchecks for dependency containers to enable waiting for them to be read/healthy before starting an application container
…abric8io#1733
Transforming the internal healthcheck model into a JSON object the Docker API understands when added to the larger create container JSON object.
poikilotherm
added a commit
to poikilotherm/docker-maven-plugin
that referenced
this issue
Dec 14, 2023
…ld time fabric8io#1733
Technically, we reuse the HealthCheckConfiguration for both build and runtime added checks. Yet the syntax is slightly different: for runtime checks, we need to specify whether we want CMD or SHELL, for build time checks Docker figures that out itself.
Description
Currently, a healthcheck can only be added to a container when building it. Existing of-the-shelve containers that are not supposed to be modified cannot be run with a healthcheck if not included by upstream image vendor. Defining healthchecks in / from Docker Compose files is not supported.
Info
mvn -v
) : 3.9.1This is fallout from #888 / #1718. It is related to #1580 . PR forthcoming.
The text was updated successfully, but these errors were encountered: