All Errors

The container health check is failing. The application inside may not be ready, the health check command may be misconfigured, or the service has crashed. Check container logs and health check output.

This error occurs when you try to pull or run a Windows container image while Docker is configured to use Linux containers. Docker Desktop on Windows can run either Linux or Windows containers, but not both simultaneously. Switch Docker to Windows container mode or use a Linux-based image instead.

This error occurs when a user tries to create an account with an email that already exists in your Firebase project. Learn how to detect this error, prompt users to log in instead, and check for existing accounts before sign-up.

This message appears when you try to merge or pull a branch that has no new commits relative to your current branch. While not technically an error, it often confuses developers when they expect changes but Git reports nothing to merge. Understanding merge direction and fetching remote changes resolves most cases.

This error occurs when pushing to a remote repository from a shallow clone, or when the remote itself is shallow and rejects updates. The fix involves unshallowing your local repository or reconfiguring the remote to accept shallow updates.

This message appears on GitHub when your forked branch has diverged from the upstream repository. Your fork contains commits not in the original repo (ahead) and is missing commits from the original (behind). Syncing your fork resolves this divergence.

npm cannot create a directory because the filesystem or policy blocks it (Windows/WSL AV locks, root-owned prefixes, read-only mounts). Use user-owned paths, release locks, and retry.

The reserved name error occurs when using PostgreSQL reserved keywords as column or table names without proper quoting. PostgreSQL distinguishes between reserved and non-reserved keywords, and reserved words cannot be used as identifiers unless wrapped in double quotes.

This error occurs when your build configuration is not properly set up to handle JSX syntax. JSX requires explicit configuration in your bundler, Babel setup, or TypeScript compiler to be transformed into valid JavaScript code that browsers can understand.

The "stdin is not a tty" message appears when SSH runs a command without allocating a terminal, typically with piped input or remote scripts. Force a TTY with the -t flag when one is genuinely needed.

This error occurs when a user with an active ban attempts to authenticate or refresh their session in Supabase. Banned users cannot log in or refresh tokens until their ban expires or is lifted.

The 'Aborting commit due to empty commit message' error occurs when Git's text editor closes without saving a commit message, or when the message file is empty. This typically happens when the configured editor doesn't wait for user input or exits prematurely.

This error occurs when Git tries to create a file with characters that are illegal on your operating system's filesystem. Windows has strict filename restrictions that Linux and macOS don't, causing cross-platform compatibility issues.

This Git error occurs when you try to push commits but the remote branch has new commits you don't have locally. Fix it by pulling remote changes first with 'git pull' or 'git pull --rebase', then push again. Force pushing should only be used when you intentionally want to overwrite remote history.

The EINTEGRITY error occurs when a downloaded package doesn't match its expected checksum. Clear npm cache and delete package-lock.json to resolve corrupted integrity hashes.

The "Missing script: build" error occurs when running npm run build but no build script is defined in package.json. Add the appropriate build command for your framework to resolve this.

This warning appears when apt detects a mismatch between the file size the server claims to send and the size recorded in the Release metadata. Usually harmless, it results from cached data or mirror synchronization delays and resolves by cleaning the apt cache and retrying.

This error occurs when attempting to execute commands on a stopped Docker container. The container exists but is not in a running state, preventing operations like exec, logs, or attach from working.

This error occurs when an asynchronous operation exceeds its configured time limit without completing. Common in network requests, database queries, and long-running async operations.

This error occurs when npm lifecycle scripts (preinstall, postinstall, prepublish, etc.) fail during package installation. These scripts are defined in package.json and run at specific stages of the installation process. Failures typically stem from missing build tools, permission issues, or incompatible dependencies.