Docker
129 incident problems in Docker environments.
먼저 읽을 가이드
추천 문제
All problems (129)
LINUX-1442A rootless image pull fails after a mirror changePulls fail only for shorthand references after a registry mirror migration.LinuxIntermediate10 minProLINUX-1455A rootless Podman service runs manually and failsA rootless Podman service runs manually and fails focuses on Runner Hygiene and asks the reader to isolate the key signal in docker. Rootless services at boot often fail because session-scoped runtime paths vanish before the unit starts.LinuxIntermediate10 minProCICD-1443A BuildKit registry cache export passes locally and fails in CIA BuildKit registry cache export passes locally and fails in CI focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. Registry edges can preserve normal pushes while quietly breaking the metadata path used fo...CI/CDIntermediate11 minProCICD-1389A package cache proxy serves old dependencies after a purgeA dependency emergency requires cache purge and later only some runners continue downloading the old package build.CI/CDIntermediate11 minProCICD-1399A package mirror warming job appears to succeed and runners still download...A package mirror warming job appears to succeed and runners still download... focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. Warm-up jobs can miss architecture-specific or conditional URLs that only...CI/CDIntermediate11 minProCICD-1458A remote cache importer works locally and misses in CIA remote cache importer works locally and misses in CI focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. Cache misses can come from registry content negotiation drift rather than from missing objects.CI/CDIntermediate11 minProCICD-1433A rootless BuildKit cache export fails (registry-front-door-rewrote-inline-cache-media-type-response)A rootless BuildKit cache export fails (registry-front-door-rewrote-inline... focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. Registry proxies can preserve ordinary push behavior and still qui...CI/CDIntermediate11 minProCICD-1423A rootless BuildKit pipeline suddenly stops exporting inline cacheA rootless BuildKit pipeline suddenly stops exporting inline cache focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. Registry proxies can preserve basic push behavior while still breaki...CI/CDIntermediate11 minProLINUX-1302A bind-mounted config file turns into a directoryA new host or deployment target launches the same container and immediately reads the wrong config shape.LinuxIntermediate12 minProCICD-1403A BuildKit digest pin is present and the build still uses the wrong baseA BuildKit digest pin is present and the build still uses the wrong base focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. Platform-specific mirror logic can undermine the guarantees you think a...CI/CDIntermediate12 minProCICD-1322A CI container reports unhealthy foreverA lean container image is deployed successfully and later flips unhealthy immediately despite serving traffic correctly.CI/CDIntermediate12 minProCICD-1393A Docker build passes locally and fails in CIA Docker build passes locally and fails in CI focuses on Identity And Access and asks the reader to isolate the key signal in docker. Runner image updates can change BuildKit mount semantics even when the Dockerfile stays untouched.CI/CDIntermediate12 minProCICD-1413A rootless BuildKit deployment on shared runners fails onlyA rootless BuildKit deployment on shared runners fails only focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. Rootless build regressions can come from an implicit storage-driver fallback after host chan...CI/CDIntermediate12 minProCICD-1371A BuildKit cache import succeeds and every merge build still goes coldA BuildKit cache import succeeds and every merge build still goes cold focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. A healthy cache import log can still be pointing at the wrong artifact type.CI/CDIntermediate13 minProCICD-1361A BuildKit job finishes and later loses cache reuseA BuildKit job finishes and later loses cache reuse focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. Stable builder names do not guarantee stable cache storage underneath.CI/CDIntermediate13 minProCICD-1325A compose dependency waits foreverA base image update lands and downstream services stop starting because a health gate never turns green anymore.CI/CDIntermediate13 minProCICD-1307A compose profile cleanup breaks startup orderingA team simplifies local profiles and later one environment hangs with no obvious container crash.CI/CDIntermediate13 minProCICD-1321A Compose stack stays unhealthy after a fixed probeAn operator fixes a bad health check command in compose and later wonders why the container still reports the old failure pattern.CI/CDIntermediate13 minProCICD-1302A container stays unhealthy forever after a bad migrationA deployment looks protected by health checks until one release wedges a service in an unhealthy-but-still-running state.CI/CDIntermediate13 minProLINUX-1303A database health check goes green before transactions are actually accepted, so dependent services migrate against a server that is still replaying recovery statePort checks pass, yet migrations fail because the real readiness condition trails behind the simplistic health command.LinuxIntermediate13 minPro