Error map
Cloud Functions: Build failed Cloud Functions: Build failed: function.js does not exist / npm install failed with exit code 1 (Cloud Build step)
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)
failed to solve: process "/bin/sh -c ..." did not complete successfully: exit code: 1
A RUN step in your Dockerfile failed. The real error is printed in the lines just above this message.
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.
Error: Node Sass does not yet support your current environment
node-sass (deprecated) has no binary for your Node version/OS.
error: subprocess-exited-with-error / Failed building wheel for x
pip had to compile a package from source and the build failed — missing compiler, headers or system libraries.
failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory
docker build can’t find a Dockerfile in the build context you passed.
Dockerfile parse error line N: unknown instruction
A line in the Dockerfile doesn’t start with a valid instruction — usually a broken line continuation or a typo.
COPY failed: file not found in build context / "/app/x": not found
The Dockerfile COPY refers to a path outside the build context, excluded by .dockerignore, or relative to the wrong directory.
Error response from daemon: max depth exceeded (too many image layers)
The image has more layers than the storage driver allows (127 for overlay2), usually from repeatedly committing containers or ver…
COPY failed: forbidden path outside the build context: ../file
A COPY/ADD tries to read a file above the build context (../something); Docker only sends the context folder to the builder.
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…
Error: @prisma/client did not initialize yet. Please run "prisma generate"
The generated Prisma Client is missing or out of date.
Error: error:0308010C:digital envelope routines::unsupported
An old build tool (webpack 4, old react-scripts) uses a hash algorithm that OpenSSL 3 in Node 17+ disables.
Two steps away (35)
E: Unable to locate package (apt / apt-get install)
apt can’t find the package name in its package lists — the lists are stale, the repository isn’t enabled, or the name is wrong fo…
Cloudflare Pages build: Error: Output directory "dist" not found / Failed: build output directory not found
The Pages build finished, but the folder set as “Build output directory” doesn’t exist — the framework wrote its files somewhere…
error NETSDK1045: The current .NET SDK does not support targeting .NET 8.0. Either target .NET 7.0 or lower, or use a version of the .NET SDK that supports .NET 8.0
The installed .NET SDK is older than the project’s TargetFramework.
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.
HTTP 408 Request Timeout
The server closed the connection because the client took too long to send the complete request.
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…
Error: Cannot find module 'x' (MODULE_NOT_FOUND)
Node can’t resolve the module path — the package isn’t installed, or a relative path/extension is wrong.
gyp ERR! build error / node-gyp rebuild failed
A dependency with native C/C++ code couldn’t compile — missing build tools, Python, or an unsupported Node version.
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './x' is not defined by "exports"
You imported a deep path inside a package that its package.json "exports" field doesn’t expose.
Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain
The Gradle wrapper JAR (gradle/wrapper/gradle-wrapper.jar) is missing or corrupt.
error: externally-managed-environment
Your system Python (Debian 12+, Ubuntu 23.04+, Homebrew) refuses pip installs into the OS-managed environment (PEP 668).
ERROR: Could not find a version that satisfies the requirement x (from versions: none)
pip found no installable version of the package for your Python version, OS or index.
error MSB3027: Could not copy "obj\...\App.dll" to "bin\...\App.dll". Exceeded retry count of 10. The file is locked by: "App (1234)"
The build can’t overwrite the output DLL/EXE because the app (or IIS Express, a test runner, antivirus) is still running and hold…
C/C++: undefined reference to `function' — collect2: error: ld returned 1 exit status
The linker can’t find the definition of a function or variable that was declared and used.
Go: runtime.main_main·f: function main is undeclared in the main package
The package is named `main` but contains no `func main()`, or you tried to build a library as an executable.
PHP Parse error: syntax error, unexpected …
PHP can’t parse the file because of a syntax mistake — the real error is often on the line before the one reported.
IndentationError: unexpected indent / expected an indented block
Python’s block structure is broken — inconsistent indentation or mixed tabs and spaces.
npm ERR! code ELIFECYCLE / Command failed with exit code 1
An npm script (build, start, test, postinstall) exited with an error. ELIFECYCLE is only the wrapper — the real error is printed…
fatal: not a git repository (or any of the parent directories): .git
You ran a Git command outside a Git working tree.
Error: ENOENT: no such file or directory
A file or directory the program tried to open doesn’t exist at that path.
exec /usr/local/bin/docker-entrypoint.sh: exec format error
The container tried to run a binary built for a different CPU architecture (arm64 vs amd64) — or a script with a broken shebang /…
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
no matching manifest for linux/arm64/v8 in the manifest list entries
The image has no build for your CPU architecture — typically pulling an amd64-only image on an Apple Silicon Mac or ARM server.
conflict: unable to remove repository reference (must force) - container is using its referenced image
You tried to delete an image that a container — even a stopped one — still uses.
Go: cgo: C compiler "gcc" not found: exec: "gcc": executable file not found in $PATH
A package using cgo needs a C compiler, but none is installed or CGO is disabled.
Go: package app/cmd: no Go files in /app/cmd / build constraints exclude all Go files
The directory you asked Go to build contains no buildable `.go` files.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
HTTP 304 Not Modified
The cached copy is still valid, so the server sends no body and the client reuses its cache.
PrismaClientKnownRequestError P2002: Unique constraint failed on the fields: (`email`)
A Prisma create/update violated a unique constraint.
Error: P1001: Can't reach database server at `host`:`5432`
Prisma couldn’t connect to the database in DATABASE_URL.
Next.js: Failed to compile. ./src/app/page.tsx 12:7 Error: 'x' is assigned a value but never used. @typescript-eslint/no-unused-vars
`next build` runs ESLint and fails the build on lint errors.
Laravel: Vite manifest not found at: public/build/manifest.json
Laravel’s @vite directive can’t find the compiled asset manifest because assets weren’t built.
'react-scripts' is not recognized as an internal or external command / react-scripts: command not found
node_modules is missing or broken, so the react-scripts binary isn’t available.
Module parse failed: Unexpected token. You may need an appropriate loader to handle this file type
Webpack found syntax it can’t parse because no loader is configured for that file (JSX, TypeScript, CSS, or modern syntax in node…
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError