Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
The Docker CLI can't connect to the Docker daemon (engine).
Practical troubleshooting guides for package manager errors across npm, Docker, and more.
The Docker CLI can't connect to the Docker daemon (engine).
Docker failed to reach the registry due to a network/timeout error.
Docker denied access to the daemon socket due to insufficient permissions.
The registry rejected the request due to authentication or permissions.
Docker failed to reach the registry due to a network/timeout error.
The container failed to start because the entrypoint/command is missing or not executable.
The container failed to start because the entrypoint/command is missing or not executable.
Docker could not find the referenced object ID (container/image/network/volume).
Docker rejected the image reference format (often because repository names must be lowercase).
Docker rejected the image reference format (often because repository names must be lowercase).
Docker failed to reach the registry due to a network/timeout error.
Docker could not find the requested image/tag/manifest (or it does not match your platform).
Docker could not find the requested image/tag/manifest (or it does not match your platform).
Docker could not find the requested image/tag/manifest (or it does not match your platform).
Docker could not find the requested image/tag/manifest (or it does not match your platform).
Docker failed to reach the registry due to a network/timeout error.
Docker could not find the requested image/tag/manifest (or it does not match your platform).
Docker failed to reach the registry due to a network/timeout error.
Docker Hub rate-limited your pulls (too many requests).
Docker could not remove a resource because it is still in use.
The registry rejected the request due to authentication or permissions.
The registry rejected the request due to authentication or permissions.
Docker could not remove a resource because it is still in use.
npm rejected the registry HTTPS certificate because it is expired.
npm rejected the registry HTTPS certificate because it was revoked.
npm couldn't validate the signature on the registry certificate chain.
npm doesn't trust the registry HTTPS certificate chain (missing CA or MITM proxy).
npm received a self-signed certificate from the registry or proxy.
npm received an authentication error (missing/invalid credentials) from the registry.
npm was authenticated, but the registry refused the request (forbidden).
npm could not find the package (or the requested version) at the configured registry.
The registry rejected the publish because the version already exists (conflict).
The registry rejected the publish payload as invalid (unprocessable entity).
npm failed due to missing filesystem permissions (EACCES).
npm could not resolve the registry hostname (DNS returned EAI_AGAIN).
The package requires a different Node.js/npm version than the one you are using (engine mismatch).
The package does not support your OS/CPU platform (platform mismatch).
npm could not modify a resource because it is busy/locked (EBUSY).
npm aborted a network request before it completed.
npm could reach the host but the TCP connection was refused.
npm lost the connection mid-request (connection reset).
npm attempted to create a file that already exists (EEXIST).
npm downloaded a package tarball whose checksum did not match the expected integrity value (lockfile/metadata mismatch).
The package name is invalid (does not follow npm naming rules).
The dist-tag name is invalid.
The version or semver range is invalid.
npm expected a file but found a directory (EISDIR).
npm could not parse `package.json` (invalid JSON).
An npm script failed (a lifecycle script exited with a non-zero status).
npm detected that the lockfile or dependency tree verification does not match what it expected.
`npm ls` detected problems in the dependency tree (missing, invalid, or extraneous packages).
npm hit the per-process open file limit (EMFILE).
npm hit a filesystem path length limit (ENAMETOOLONG).
npm requires authentication to access the package or registry.
The system hit the global open file limit (ENFILE).
npm referenced a file or directory that does not exist (ENOENT).
npm rejected the command usage or configuration (invalid usage).
npm ran out of disk space while writing files (ENOSPC).
npm expected a directory but found a file (ENOTDIR).
npm tried to remove a directory that is not empty (ENOTEMPTY).
npm could not resolve the registry hostname (DNS returned ENOTFOUND).
npm requires a one-time password (2FA) for this operation.
npm failed due to an operation not permitted by the OS (EPERM).
npm tried to write to stdout/stderr but the output stream was closed (broken pipe / EPIPE).
The registry rejected the publish because the version already exists (publish conflict).
npm could not resolve a compatible dependency tree (often peer dependency conflicts).
npm tried to write to a read-only filesystem (EROFS).
npm hit a socket timeout while waiting for registry/network I/O.
npm could not find a version that matches the requested semver range or dist-tag.
npm timed out while connecting to the registry or downloading a tarball.
npm rejected the command usage or configuration (invalid usage).
npm connected to a host whose certificate doesn't match the hostname (CN/SAN mismatch).
npm saw a self-signed certificate somewhere in the TLS certificate chain.
npm couldn't find the issuer certificate needed to build a trusted chain.
npm couldn't find the issuer certificate in the local trust store.
npm couldn't verify the registry TLS certificate chain (missing CA/intermediate, or an intercepting proxy).
Maven cannot download or resolve one or more dependencies required by the project.
Maven could not download or parse the POM for a dependency/plugin, so it cannot resolve that artifact's transitive dependencies.
Maven could not find an artifact in the configured repositories, and the missing result may be cached in the local repository.
Maven cannot resolve the `<parent>` POM for your project from the local filesystem or configured repositories.
You ran a Maven goal that needs a `pom.xml`, but Maven cannot find one in the current directory (or via `-f`).
Maven attempted to download an artifact or metadata from a repository, but the HTTP(S) transfer failed.
The JVM running Maven cannot validate the HTTPS certificate chain of the repository, so Maven refuses the connection.
The repository requires authentication, but Maven did not send valid credentials for the repository `<id>` being used.
The repository rejected the request (403). Your credentials may be valid, but you are not authorized for that repository/path or operation.
Maven is using an HTTP proxy to reach repositories, but the proxy requires authentication and Maven is not configured with valid proxy credentials.
Maven cannot map a short plugin prefix (like `spring-boot`) to an actual plugin artifact, usually because the plugin isn't available from configured plugin repositories or isn't declared in the build.
Maven cannot download a build plugin (or its transitive dependencies) from configured plugin repositories.
Maven cannot write to the local repository directory (`~/.m2/repository` by default), usually due to permissions or a read-only filesystem.
Maven downloaded an artifact, but its checksum did not match (or the repository did not provide expected checksums), indicating corruption or repository/proxy issues.
Maven refused to use an insecure HTTP repository URL and blocked the request using the built-in `maven-default-http-blocker` mirror.
Maven located a JAR coordinate, but could not download the corresponding POM, so it cannot determine transitive dependencies or metadata for that artifact.
The machine running Maven could not resolve the repository hostname via DNS, so Maven cannot download artifacts or metadata.
The JVM running Maven could not complete the TLS handshake with the repository, so Maven cannot download artifacts over HTTPS.
Maven is running with offline mode enabled (`-o` / `--offline`), so it will not contact remote repositories to download missing artifacts.
Your shell can't find a `pip` executable on `PATH` (or you're using an environment where `pip` is intentionally not installed).
On Windows, `cmd.exe`/PowerShell can't find `pip.exe` on PATH (or you're using the wrong Python install).
Your OS Python is marked as "externally managed" (PEP 668), so pip refuses to modify the system environment outside a virtual environment.
The Python interpreter you're running does not have pip installed (or the environment is broken/corrupted).
pip does not have `update` or `upgrade` subcommands. Upgrading packages is done with `pip install --upgrade ...`.
You ran `pip install` without specifying a package name, a file/path, or `-r requirements.txt`.
You're running pip through an outdated entrypoint script. It still works today, but it can break after pip upgrades.
pip was asked to install from a requirements file path that does not exist (wrong filename, wrong directory, or missing checkout).
pip could not parse a requirement specifier (malformed version constraint, quotes/smart-quotes, comments, or an invalid line in a requirements file).
You asked pip to install from a local directory or sdist, but it doesn't contain standard Python packaging metadata (`pyproject.toml` or `setup.py`).
pip could not find any installable release that matches your requirement and your environment (Python version, OS/architecture, and index configuration).
The package (or one of its dependencies) declares a `Requires-Python` range that excludes the Python interpreter you're using.
pip's resolver could not find any set of versions that satisfies all constraints at the same time.
Your environment is already inconsistent. pip installed or upgraded something, but the full installed set now contains version conflicts.
pip delegated part of the install to an external build step (PEP 517 backend or legacy `setup.py`) and that subprocess failed.
pip attempted to build a wheel from a PEP 517 project, but the wheel build failed and pip cannot install it without a wheel.
pip is building a package from source, but your system is missing a required toolchain (C/C++ compiler, Python headers, MSVC Build Tools, or Rust).
pip tried to write into a directory you don't have permission to modify (often system site-packages or a protected install directory).
The machine ran out of disk space while pip was downloading/building/installing packages (often in the temp directory or cache).
pip detected that its cache directory is owned by a different user (often because pip was previously run with `sudo`), so it disables caching for safety.
Your Python was built or installed without SSL support, so pip cannot make HTTPS requests to package indexes like PyPI.
pip is repeatedly failing to reach the package index due to network timeouts, proxy issues, or TLS incompatibilities, and it is retrying until it gives up.
You are using hash-checking mode (`--require-hashes`), but the downloaded file's hash doesn't match, or some requirements are missing hashes.
pip cannot uninstall a package because it cannot find the installed-files manifest (`RECORD`) in the package metadata.
pip refuses to uninstall a package that was installed via distutils/OS tooling without reliable metadata, because it can't safely determine which files to remove.
pip detected a corrupted or incompatible cache entry and ignored it. Installs may be slower or may fail if corruption is widespread.