Behaviour when container HealthStartPeriod < HealthStartInterval is unintuitive #46747
Labels
area/api
area/runtime
kind/bug
Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.
version/master
Milestone
Description
The daemon waits for
HealthStartInterval
to elapse before it performs the next probe, even ifHealthStartPeriod
ends before that time.Reproduce
Run a container with a health-check, e.g.:
The container's health status will become
unhealthy
~30s after the container is started.Expected behavior
The container's health status becomes
unhealthy
within oneInterval
afterStartPeriod
has elapsed since the container has started.docker version
Client: Cloud integration: v1.0.35+desktop.5 Version: 24.0.6 API version: 1.43 Go version: go1.20.7 Git commit: ed223bc Built: Mon Sep 4 12:28:49 2023 OS/Arch: darwin/arm64 Context: desktop-linux Server: Docker Desktop 4.24.2 (124339) Engine: Version: dev API version: 1.44 (minimum version 1.12) Go version: go1.20.8 Git commit: HEAD Built: Tue Sep 26 11:52:32 2023 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.6.22 GitCommit: 8165feabfdfe38c65b599c4993d227328c231fca runc: Version: 1.1.8 GitCommit: v1.1.8-0-g82f18fe docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Additional Info
The text was updated successfully, but these errors were encountered: