Error map
Mounts denied Docker Desktop: Mounts denied: The path is not shared from the host and is not known to Docker
Docker · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (6). 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.
Directly related (6)
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…
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.
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.
invalid mount config for type "bind": bind source path does not exist
A -v/--mount or Compose volume points at a host path that doesn’t exist (from the Docker daemon’s point of view).
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.
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 (18)
npm ERR! code EACCES — permission denied
npm can’t write to a directory — usually global installs into a root-owned folder.
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.
Linux: Permission denied
Your user (or the service user) lacks read/write/execute permission on a file, directory or one of its parents.
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
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…
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…
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.
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.
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.
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.
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.
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.
fatal: not a git repository (or any of the parent directories): .git
You ran a Git command outside a Git working tree.
Author identity unknown *** Please tell me who you are.
Git doesn’t know your name and email for commits.
error: unable to create file x: Filename too long (Windows)
Windows’ 260-character path limit blocked Git from creating a file.
Stack is in ROLLBACK_COMPLETE state and can not be updated
The stack’s first creation failed and rolled back; a stack in ROLLBACK_COMPLETE can only be deleted, not updated.
CloudFormation stack in UPDATE_ROLLBACK_FAILED
An update failed, and then the rollback also failed, leaving the stack stuck until you continue the rollback.
Elastic Beanstalk: Environment health has transitioned from Ok to Severe
Most instances in the Elastic Beanstalk environment are failing health checks or returning errors.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException