OhSudo — new Docker & Containers articlesNew Docker & Containers articles from OhSudo: practical fixes for DevOps engineers, SysAdmins and IT folks.https://ohsudo.com/en-usDocker "pull access denied": the repository doesn't exist, or you're not logged inhttps://ohsudo.com/articles/docker-pull-access-denied-repository-does-not-exist/https://ohsudo.com/articles/docker-pull-access-denied-repository-does-not-exist/Fix Docker "pull access denied, repository does not exist or may require docker login": check the image name and tag, log in to the right registry, handle rate limits.Sun, 08 Nov 2026 00:00:00 GMTDocker & Containersdockerregistrydocker-loginimagesghcrtroubleshootingcontact@ohsudo.com (OhSudo)Alpine "not found" for a binary that's right there: glibc vs muslhttps://ohsudo.com/articles/alpine-binary-not-found-glibc-musl/https://ohsudo.com/articles/alpine-binary-not-found-glibc-musl/A binary exists on Alpine, yet running it says "not found" or "no such file or directory": it was built for glibc. Check with ldd, then rebuild it or use gcompat.Fri, 06 Nov 2026 00:00:00 GMTDocker & Containersalpinedockermuslglibccontainerstroubleshootingcontact@ohsudo.com (OhSudo)Docker "exec format error": the wrong CPU architecture, or a script with no shebanghttps://ohsudo.com/articles/docker-exec-format-error/https://ohsudo.com/articles/docker-exec-format-error/Fix Docker "exec /app: exec format error": an image built for another architecture (arm64 vs amd64) or a script with no shebang. Check it, then build with buildx.Fri, 06 Nov 2026 00:00:00 GMTDocker & Containersdockerarm64amd64buildxmulti-platformtroubleshootingcontact@ohsudo.com (OhSudo)Docker "port is already allocated" and "ports are not available": find who has the porthttps://ohsudo.com/articles/docker-port-is-already-allocated/https://ohsudo.com/articles/docker-port-is-already-allocated/Fix Docker "Bind for 0.0.0.0:8080 failed: port is already allocated" and "Ports are not available": find the container or process using it, and Windows reserved ports.Fri, 06 Nov 2026 00:00:00 GMTDocker & Containersdockerdocker-composeportswindowswsltroubleshootingcontact@ohsudo.com (OhSudo)"Cannot connect to the Docker daemon. Is the docker daemon running?": every causehttps://ohsudo.com/articles/cannot-connect-to-the-docker-daemon/https://ohsudo.com/articles/cannot-connect-to-the-docker-daemon/Fix "Cannot connect to the Docker daemon. Is the docker daemon running?": start the service, read why it failed, check DOCKER_HOST, contexts, Docker Desktop and WSL.Thu, 05 Nov 2026 00:00:00 GMTDocker & Containersdockerdockerdsystemddocker-desktopwsltroubleshootingcontact@ohsudo.com (OhSudo)Docker build "failed to compute cache key: … not found": why COPY can't see your filehttps://ohsudo.com/articles/docker-build-failed-to-compute-cache-key-not-found/https://ohsudo.com/articles/docker-build-failed-to-compute-cache-key-not-found/Fix "failed to compute cache key … not found" and "COPY failed": the file is outside the build context, excluded by .dockerignore, or missing in CI.Wed, 04 Nov 2026 00:00:00 GMTDocker & Containersdockerdockerfilebuildkitdockerignorecitroubleshootingcontact@ohsudo.com (OhSudo)Docker: "connection refused" to localhost from a container — how to reach the hosthttps://ohsudo.com/articles/docker-container-connect-to-localhost/https://ohsudo.com/articles/docker-container-connect-to-localhost/Fix "connection refused" when a container connects to localhost: use host.docker.internal or a Compose service name, make the host service listen, and check the firewall.Mon, 02 Nov 2026 00:00:00 GMTDocker & Containersdockerdocker-composenetworkinglocalhosthost-gatewaytroubleshootingcontact@ohsudo.com (OhSudo)Docker: "permission denied while trying to connect to the Docker daemon socket"https://ohsudo.com/articles/docker-permission-denied-docker-sock/https://ohsudo.com/articles/docker-permission-denied-docker-sock/Fix Docker "permission denied" on /var/run/docker.sock: add your user to the docker group, make it take effect, and know why chmod 666 is a bad idea.Mon, 02 Nov 2026 00:00:00 GMTDocker & Containersdockerpermissionsgroupslinuxtroubleshootingcontact@ohsudo.com (OhSudo)Docker "exited with code 137": OOM kill or a stop that took too longhttps://ohsudo.com/articles/docker-container-exited-with-code-137/https://ohsudo.com/articles/docker-container-exited-with-code-137/Exit code 137 means the container was killed with SIGKILL. Find out if it ran out of memory or ignored docker stop, and fix each case.Sun, 01 Nov 2026 00:00:00 GMTDocker & Containersdockerdocker-composeoommemorysignalstroubleshootingcontact@ohsudo.com (OhSudo)