Error map

bind source path does not exist invalid mount config for type "bind": bind source path does not exist

Docker · layer 6, Platform & cloud

Centre: this error. First ring: errors it is linked with (9). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.

1 · On your device 2 · Network 3 · Edge & web server 4 · Application & API 5 · Data 6 · Platform & cloud 7 · Build & delivery

Directly related (9)

lookup registry-1.docker.io: no such hostDocker

dial tcp: lookup registry-1.docker.io: no such host / Temporary failure in name resolution during docker build

DNS isn’t working for the Docker daemon or inside build containers, so pulls and package downloads fail.

permission denied (volume)Docker

Permission denied writing to a mounted volume inside a Docker container

The process inside the container runs as a user (UID) that doesn’t own the bind-mounted host folder, so reads/writes fail with EA…

Mounts deniedDocker

Docker Desktop: Mounts denied: The path is not shared from the host and is not known to Docker

Docker Desktop (macOS) can only bind-mount folders listed under Settings → Resources → File sharing.

FailedMountKubernetes

Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition

The kubelet couldn’t mount one of the pod’s volumes, so the pod stays in ContainerCreating.

PVC PendingKubernetes

PersistentVolumeClaim stuck in Pending (no persistent volumes available / waiting for first consumer)

The PVC hasn’t been bound to a volume, so pods using it can’t be scheduled.

could not select device driverDocker

could not select device driver "" with capabilities: [[gpu]]

docker run --gpus was used, but the NVIDIA Container Toolkit isn’t installed/configured, so Docker can’t expose the GPU.

client version is too newDocker

Error response from daemon: client version 1.45 is too new. Maximum supported API version is 1.41

Your Docker CLI (or SDK) speaks a newer API version than the Docker daemon it’s talking to.

Sending build contextDocker

Docker build slow: "Sending build context to Docker daemon 2.5GB" / transferring context takes forever

docker build is uploading your whole project folder — node_modules, .git, data files — before building, because there’s no (or a…

Multi-Attach errorKubernetes

Multi-Attach error for volume: Volume is already exclusively attached to one node and can't be attached to another

A ReadWriteOnce volume (EBS, Azure Disk, PD) is still attached to another node, so the new pod on a different node can’t use it.

Two steps away (22)

ECONNREFUSEDNode.js

Error: connect ECONNREFUSED 127.0.0.1:5432

Nothing is listening at that host:port — the target service is down or you’re connecting to the wrong address.

408HTTP

HTTP 408 Request Timeout

The server closed the connection because the client took too long to send the complete request.

Failed to fetchJavaScript

TypeError: Failed to fetch / NetworkError when attempting to fetch resource

The browser couldn’t complete the request at the network level — CORS, DNS, offline, blocked mixed content, or the server refused…

EACCESnpm

npm ERR! code EACCES — permission denied

npm can’t write to a directory — usually global installs into a root-owned folder.

daemonDocker

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

The docker CLI can’t talk to the Docker engine — it isn’t running, or your user can’t access the socket.

EACCESLinux

Linux: Permission denied

Your user (or the service user) lacks read/write/execute permission on a file, directory or one of its parents.

WSL 2 installation is incompleteDocker

Docker Desktop: WSL 2 installation is incomplete / WSL update required

Docker Desktop on Windows needs WSL 2 and its Linux kernel; they’re missing, outdated or disabled.

CrashLoopBackOffKubernetes

Kubernetes: CrashLoopBackOff

The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.

AuthorizationPermissionMismatchAzure

Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission

You’re accessing blob/queue data with Microsoft Entra ID, but the identity has only management roles (Owner/Contributor) — not a…

CreateContainerConfigErrorKubernetes

Kubernetes: CreateContainerConfigError — secret / configmap not found

Kubernetes can’t build the container’s configuration — usually a referenced Secret, ConfigMap or key doesn’t exist in that namesp…

FailedSchedulingKubernetes

Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available

The scheduler can’t find a node that satisfies the pod’s resource requests, selectors, taints or volume constraints.

QuotaExceededErrorJavaScript

QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value exceeded the quota

localStorage/sessionStorage is full (about 5 MB per origin) or storage is disabled.

126 incorrect key fileMySQL

MySQL ERROR 126 (HY000): Incorrect key file for table; try to repair it

MySQL can’t use a table’s index file — usually a full tmp disk during a query, or MyISAM corruption.

the attribute version is obsoleteDocker

WARN: the attribute `version` is obsolete, it will be ignored

A harmless Compose v2 warning: the top-level version: line in docker-compose.yml is no longer used.

You cannot remove a running containerDocker

Error response from daemon: You cannot remove a running container. Stop the container before attempting removal or force remove

docker rm refuses to delete a container that is still running.

EPUBLISHCONFLICTnpm