Error map
Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
Google Cloud / Firebase · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (12). 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 (12)
System has not been booted with systemd as init system (PID 1). Can't operate.
You ran systemctl inside an environment without systemd as PID 1 — a Docker container or older WSL.
Docker: Bind for 0.0.0.0:80 failed: port is already allocated
Another container or host process already publishes that host port.
OCI runtime create failed: exec: "x": executable file not found in $PATH
The command you asked the container to run doesn’t exist inside the image — wrong command name, a shell that isn’t installed (bas…
Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
Firestore Security Rules denied the read/write — the user isn’t signed in, the rule conditions don’t match, or test-mode rules ex…
Error response from daemon: Container X is not running
You tried to exec into or interact with a container that has stopped.
Azure Container Registry: unauthorized: authentication required, visit https://aka.ms/acr/authorization (AKS ErrImagePull 401)
Pulling/pushing to ACR wasn’t authenticated — Docker not logged in, or AKS/App Service lacks AcrPull on the registry.
npm ERR! code EROFS — EROFS: read-only file system
npm tried to write to a read-only location (read-only container filesystem, mounted volume, or system path).
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
Conflict. The container name "/x" is already in use by container …
A container (running or stopped) already has that name; Docker won’t create a second one with the same name.
Pod status CreateContainerError
The image was pulled, but the container runtime failed to create the container — bad command, missing mount target, or a name/vol…
Pod status RunContainerError
The container was created but failed to start — usually an invalid command/entrypoint, missing interpreter, or permission problem…
Google Cloud: Error: Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started
The Google client library found no Application Default Credentials (ADC) on this machine or environment.
Two steps away (34)
ECS task stopped: CannotPullContainerError: pull image manifest has been retried ... / ref pull has been retried
The ECS task couldn’t pull its image — no network route to the registry, missing ECR permissions, or a wrong image tag.
Docker container exits immediately (Exited (0) / Exited (1) right after start)
The container started and its main process finished at once, so the container stopped — Docker containers only live as long as PI…
Job for nginx.service failed because the control process exited with error code
systemd tried to start the service, but its start command failed. The real reason is in the service’s status/journal.
Error: listen EADDRINUSE: address already in use :::3000
Another process is already listening on that port.
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.
Web server failed to start. Port 8080 was already in use.
Spring Boot couldn’t bind its embedded server port because another process uses it.
bash: command not found
The shell can’t find an executable with that name in any directory on your PATH.
exec /docker-entrypoint.sh: no such file or directory (CRLF line endings / missing interpreter)
The entrypoint file exists, but the kernel can’t run it — almost always Windows CRLF line endings in the script, or a shebang poi…
exec /entrypoint.sh: permission denied (container won't start)
The entrypoint or command isn’t marked executable inside the image, or it’s on a volume mounted noexec.
PERMISSION_DENIED: The caller does not have permission (insufficient permissions)
You are authenticated, but your identity isn’t allowed to perform this action on this resource.
Firebase Auth: auth/invalid-credential (auth/wrong-password, auth/user-not-found, auth/invalid-login-credentials)
Firebase rejected the email/password sign-in — wrong password, no such user, or a provider credential that’s malformed/expired.
ECS: Essential container in task exited (task keeps stopping)
The main (essential) container stopped, so ECS stopped the whole task and the service keeps replacing it.
docker: invalid reference format (repository name must be lowercase)
Docker couldn’t parse the image name — uppercase letters, spaces, an empty variable, or a misplaced option.
Error response from daemon: No such container
The container name or ID you used doesn’t exist on this Docker host — it was removed, has another name, or you’re talking to a di…
Kubernetes: ImagePullBackOff / ErrImagePull
The node can’t pull the container image — wrong name/tag, missing registry credentials, or registry unreachable.
denied: Your authorization token has expired. Reauthenticate and try again. (Amazon ECR)
Docker’s login to Amazon ECR has expired — ECR tokens last 12 hours, so pushes and pulls fail until you log in again.
unauthorized: authentication required (docker push / pull)
The registry needs credentials for this operation and the request had none or had expired ones.
Linux: Permission denied
Your user (or the service user) lacks read/write/execute permission on a file, directory or one of its parents.
java.io.FileNotFoundException: config.properties (No such file or directory)
Java couldn’t open the file — wrong path relative to the working directory, missing file, or a classpath resource read as a file.
java.nio.file.NoSuchFileException: /path/file
An NIO Files operation targeted a path that doesn’t exist.
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
Azure App Service: ":( Application Error" / container didn’t respond to HTTP pings
App Service started your app but it crashed or never listened on the expected port.
Docker container is unhealthy (health check failing)
The container is running, but its HEALTHCHECK command keeps failing, so Docker (and dependent services) consider it unhealthy.
Docker container keeps restarting (Restarting (1) x seconds ago)
The container crashes on start and its restart policy (always/unless-stopped/on-failure) starts it again in a loop.
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.
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…
Pod status InvalidImageName: couldn't parse image reference
The image field in the pod spec isn’t a valid image reference, so the kubelet can’t even try to pull it.
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.
Pod status Init:CrashLoopBackOff / Init:Error
An init container keeps failing, so the pod’s main containers never start.
Error from server (BadRequest): container "x" in pod "y" is waiting to start: ContainerCreating
kubectl logs has nothing to show yet — the container hasn’t started (still creating, pulling, or blocked).
Git: Permission denied (publickey). fatal: Could not read from remote repository.
SSH authentication to GitHub/GitLab/Bitbucket failed — no key, wrong key, or the key isn’t added to your account.
Azure AD (Entra ID): AADSTS700016 Application not found in the directory
The client ID in your sign-in request doesn’t exist in the tenant you’re authenticating against.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException