Docker errors

• Bind for 0.0.0.0:8080 failed: port is already allocatedAnother container or process already uses that host port. Stop it, or publish your container on a different port.
• Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?The Docker CLI can't reach the daemon. Start the Docker service (or Docker Desktop), and check you're using the right context.
• Conflict. The container name is already in use by containerA container with that name already exists (often stopped). Remove it, start it instead, or run with --rm next time.
• COPY failed: file not found in build contextDocker can only COPY files that are inside the build context (the folder you pass to docker build, usually "."). The file is outside it, excluded by .dockerignore, or the path is wrong.
• docker-compose: command not foundCompose v1 (the separate docker-compose binary) is deprecated and often not installed. Modern Docker ships Compose v2 as a plugin, run as "docker compose" with a space. If that also fails, install the compose plugin.
• error getting credentials - err: exec: "docker-credential-desktop": executable file not found in $PATHDocker's config.json tells it to use a credential helper (credsStore) that isn't installed or can't run, so every pull, build or login fails. Fix or remove the credsStore entry in ~/.docker/config.json.
• Error response from daemon: network not foundA container or Compose project refers to a Docker network that no longer exists, usually because it was removed (`docker network prune`, `compose down`) or recreated with a new ID while the container still points to the old one.
• exec format errorThe container's binary was built for a different CPU architecture (arm64 vs amd64), or the script has no valid shebang line.
• failed to solve: process "/bin/sh -c ..." did not complete successfully: exit code: 1A RUN instruction in your Dockerfile returned a non-zero exit code, so BuildKit stopped the build. The real error is printed above this line, in the output of that step.
• manifest unknownThe registry exists and you can reach the repository, but the tag (or digest) you asked for doesn't exist there. Usually a missing `latest` tag, a typo in the tag, or an image that was never pushed.
• no matching manifest for linux/arm64/v8 in the manifest list entriesThe image you pulled has no build for your CPU architecture (often Apple Silicon / ARM pulling an amd64-only image, or the reverse). Use a multi-arch tag, emulate with --platform, or build the image yourself.
• no space left on device (Docker)Docker has filled the disk with old images, containers, volumes and build cache. Check usage with docker system df and prune.
• OCI runtime create failed: exec: executable file not found in $PATHThe command Docker was told to run (CMD, ENTRYPOINT, or the docker run/exec argument) doesn't exist inside the image's filesystem or $PATH. Common with bash on Alpine/distroless images or a malformed CMD.
• permission denied while trying to connect to the Docker daemon socketYour user isn't allowed to talk to the Docker daemon. Add yourself to the docker group and start a new login session.
• pull access denied for X, repository does not exist or may require 'docker login'Docker tried to pull the image from a registry and was refused. Usually the image name is wrong or was never built locally, it lives in a private repository you haven't logged in to, or the registry/namespace prefix is missing.
• standard_init_linux.go: exec user process caused: no such file or directoryThe container's entrypoint exists, but the kernel can't run it because its interpreter (from the shebang line) or dynamic loader is missing. Usually Windows CRLF line endings, a bash script on an image without bash, or a glibc binary on Alpine.
• toomanyrequests: You have reached your pull rate limit.Docker Hub limits how many image pulls an IP address (anonymous) or account can make in a time window. CI runners and shared NAT IPs hit it quickly. Log in, cache images, or pull from a mirror.
• unauthorized: authentication requiredThe registry rejected your pull or push because you're not logged in, your credentials or token expired, or you're pushing to a repository name your account can't write to.