Error map
permission denied /var/run/docker.sock Jenkins: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock
CI/CD · layer 7, Build & delivery
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.
Directly related (9)
Jenkins: WorkflowScript: 12: unexpected token: } @ line 12, column 5. 1 error
The Jenkinsfile has a Groovy/Declarative syntax error, so the build fails before running any stage.
Jenkins: Still waiting to schedule task — Waiting for next available executor / 'agent1' is offline
A Jenkins build is queued because no executor with the required label is free or the agent is offline.
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.
GitLab CI: Cannot connect to the Docker daemon at tcp://docker:2375. Is the docker daemon running?
A docker-in-docker job could not reach the `docker:dind` service — it is not started, not privileged, or the TLS/host settings do…
GitHub Actions: Error: Cannot perform an interactive login from a non TTY device
`docker login` asked for a password interactively, but CI has no terminal — pass credentials non-interactively.
Jenkins: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String toUpperCase
A sandboxed Pipeline script called a method that has not been approved in Script Security.
Jenkins: ERROR: Could not find credentials entry with ID 'github-token'
The Jenkinsfile references a credentials ID that does not exist in the scope Jenkins can see for this job.
GitLab CI: ERROR: Job failed: failed to pull image "registry.example.com/app:latest" with specified policies [always]: access forbidden
The runner could not pull the job's Docker image — authentication, a wrong name or tag, or a registry rate limit.
Jenkins: java.lang.NoSuchMethodError: No such DSL method 'dockerBuild' found among steps
The Jenkinsfile calls a step that does not exist — the plugin is not installed, or the name or argument is wrong.
Two steps away (19)
GitHub Actions: Invalid workflow file: .github/workflows/ci.yml#L12 — You have an error in your yaml syntax on line 12
GitHub could not parse your workflow YAML, so no run was created — usually indentation, a tab, or an unquoted special character.
Argo CD: ComparisonError: rpc error: code = Unknown desc = Manifest generation error (cached): kustomize build failed
Argo CD could not render the manifests (Helm, Kustomize or plain YAML) for the application, so it cannot compare Git with the clu…
GitLab CI: This job is stuck because you don't have any active runners online or available with any of these tags assigned to them
No GitLab runner can pick up the job — runners are offline, the job’s tags don’t match any runner, or shared runners are disabled.
GitHub Actions: Waiting for a runner to pick up this job… (job stays queued — No runner matching the specified labels)
The job is queued and never starts — no available runner has all the labels in `runs-on`, runners are offline/busy, or the hosted…
Bitbucket Pipelines: Container 'Build' exceeded memory limit / Docker container exited with code 137
A Bitbucket Pipelines step used more memory than the step allows (4 GB by default, 1 GB for service containers) and was killed.
MySQL ERROR 2002 (HY000): Can't connect to local MySQL server through socket
The client couldn’t reach the MySQL server — it isn’t running, or the client is looking for the socket/port in the wrong place.
Docker: Bind for 0.0.0.0:80 failed: port is already allocated
Another container or host process already publishes that host port.
Linux: Permission denied
Your user (or the service user) lacks read/write/execute permission on a file, directory or one of its parents.
GitLab CI: Found errors in your .gitlab-ci.yml: jobs:build config contains unknown keys: scripts
GitLab rejected the pipeline configuration, so no pipeline was created — the message names the job and the problem.
GitLab CI: ERROR: Uploading artifacts as "archive" to coordinator... too large archive id=123 responseStatus=413 Request Entity Too Large
The job produced an artifact bigger than the instance or project's maximum artifact size.
GitLab CI: This job could not start because it could not retrieve the needed artifacts (dependencies: build).
A job needs artifacts from an earlier job, but that job failed, was skipped or its artifacts have expired or been deleted.
denied: requested access to the resource is denied (docker push)
You’re logged in, but not allowed to push to that repository — usually the image isn’t tagged with your own username/organisation.
GitHub Actions: Error: Resource not accessible by integration (403)
The workflow’s GITHUB_TOKEN doesn’t have the permission needed for that API call (comment, push, create release, write packages).
GitHub Actions: Cache not found for input keys: npm-Linux-abc123 / Failed to save: Unable to reserve cache with key, another job may be creating this cache
`actions/cache` either found nothing for your key (restore miss) or could not save because another run is already saving the same…
Azure Pipelines: /azure-pipelines.yml: File /templates/build.yml not found in repository / Unable to find template
The YAML references a template (`template: templates/build.yml`) that Azure cannot find — wrong path, repo resource or branch.
GitHub Actions: Error: Input required and not supplied: token
An action needs an input (token, ssh-key, api-key…) and the `with:` value is empty or missing — often because the secret does not…
GitLab CI: ERROR: Job failed: execution took longer than 1h0m0s seconds
The job ran past its timeout (project default is 60 minutes) and GitLab killed it.
GitLab CI: No pipeline created — pipeline filtered out by workflow:rules / "The rules configuration prevented any jobs from being added to the pipeline"
Your `workflow:rules` or job-level `rules:` evaluated to "never" for this event, so GitLab created no pipeline or no jobs.
GitLab CI: ERROR: Job failed: exit code 1
The last command in the job's `script` returned a non-zero status; the real error is printed earlier in the job log.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError