Docker cgroup Memory Limit Not Enforced
Docker cgroup memory limits are not enforced when kernel memory accounting is disabled.
Category archive
Published troubleshooting guides for docker issues.
Docker cgroup memory limits are not enforced when kernel memory accounting is disabled.
Docker user namespace remapping causes permission errors on volume mounts.
Docker container fails to write when filesystem is mounted read-only.
Docker image layers become corrupted after interrupted pull or build operations.
Docker runc fails to execute container when OCI specification is violated.
Docker containerd shim becomes unresponsive when runtime is stuck or resources exhausted.
Docker Hyper-V NAT networking fails when vSwitch is misconfigured.
Docker Windows container fails when volume paths use Unix-style instead of Windows paths.
Docker entrypoint override is ignored when ENTRYPOINT uses exec form incorrectly.
Docker build argument is not substituted when ARG is declared after usage or scope is wrong.
Docker leaves zombie proxy processes that consume resources after container removal.
Docker container traffic is blocked when iptables FORWARD chain policy is DROP.
Docker container hosts file is stale when linked containers are recreated.
Docker BuildKit builds are slower than expected when cache is misconfigured.
Docker content trust verification fails when image signature is invalid or expired.
Docker registry garbage collection removes layers still referenced by manifests.
Docker container cannot start new processes when PID namespace limit is reached.
Docker container runs out of file descriptors when ulimit is set too low.
Docker container operations are denied when AppArmor profile blocks specific actions.
Docker container fails system calls when seccomp profile is too restrictive.
Docker build does not benefit from layer caching when Dockerfile instructions are poorly ordered.
Docker build is slow when build context includes unnecessary files from .dockerignore.
Docker container cannot access NVIDIA GPU when nvidia-container-toolkit is not installed.
Docker IPv6 networking fails when daemon is not configured with ipv6 and fixed-cidr-v6.
Docker macvlan network isolates containers from host when L2 switching is misconfigured.
Docker container continuously restarts due to application crashes or misconfigured entrypoint.
Docker cannot find specified image tag when it does not exist in the registry.
Docker container cannot reach host services when host networking is blocked by firewall rules.
Docker overlay2 storage driver becomes corrupted after unclean shutdown or disk errors.
Docker rootless mode fails when user namespace mappings or systemd scope are misconfigured.
Docker container shows incorrect timezone when TZ environment variable is not set.
Docker Swarm manager loses connectivity to worker nodes due to network partition or firewall rules.
Docker Swarm service remains in Pending state when no nodes satisfy placement constraints.
Docker container DNS resolution fails when docker0 bridge or resolv.conf is misconfigured.
Docker container health check continuously reports unhealthy when command is misconfigured.
Docker multi-stage build fails due to missing artifacts, path errors, or build argument issues.
Docker image build fails when build cache or intermediate layers consume all available space.
Docker container logs are empty or not updating when logging driver is misconfigured.
Docker container consumes excessive CPU due to application bugs, crypto mining malware, or misconfiguration.
Docker container cannot bind to host port when another process is already using it.
Docker cannot authenticate to private registry due to expired credentials or misconfigured auth.
Docker container is terminated by OOM killer when memory limits are exceeded.
Docker Compose fails to start services due to dependency.net issues, missing images, or configuration errors.
Docker container cannot access mounted volume due to SELinux, AppArmor, or filesystem permissions.
Docker container networking fails when bridge network is misconfigured or iptables rules block traffic.
Docker consumes all available disk space through image cache, container logs, and volumes.
Docker image pull times out due to network connectivity, registry unavailability, or large image size.
Docker container exits with code 0 or 1 when the main process completes or encounters an error.
Docker daemon fails to start due to storage driver issues, configuration errors, or port conflicts.