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
Bump as part of release cycles; the digest is the source of truth.
38
40
41
+
## Container healthcheck on the distroless run image
42
+
43
+
On Docker Compose the container `HEALTHCHECK` is the only container-level health signal —
44
+
`service_healthy` gating and the `docker compose ps` column both depend on it. `run-tiny` has no
45
+
shell/wget and `builder-noble-java-tiny` bundles no probe, so `pom.xml` adds an explicit `<buildpacks>`
46
+
order. Specifying `<buildpacks>`**replaces** the builder's default order, so the `java` composite must
47
+
be re-listed (`urn:cnb:builder:paketo-buildpacks/java`) before appending
48
+
`docker://paketobuildpacks/health-checker`; `BP_HEALTH_CHECKER_ENABLED=true` opts it in. It contributes
49
+
the static, shell-free `thc` binary at `/workspace/health-check`, which the compose services invoke as an
50
+
exec-form `HEALTHCHECK` (`THC_PORT`/`THC_PATH` → actuator liveness/readiness). No `health-check` process
51
+
type is added, so the JVM-spawn-per-probe issue (health-checker#87) does not apply.
52
+
39
53
## git CLI in the runtime image
40
54
41
55
`GitDiffOperations` previously shelled out to `git`; it was ported to JGit in the prerequisite commit, eliminating the runtime `git` dependency. The Paketo run image is used unmodified.
0 commit comments