https://fixercode.com Independent reference for web, software, and OS errors with clear explanations and context. en-us Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/cannot-connect-to-the-docker-daemon The docker binary is a client that forwards every request to a background daemon over a Unix socket or a TCP endpoint. When the socket file is missing, the daemon process is stopped, or DOCKER_HOST points at an unreachable host, the client prints this message and exits without attempting anything. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/cannot-connect-to-the-docker-daemon https://fixercode.com/software/docker/core/permission-denied-docker-socket On Linux the daemon listens on /var/run/docker.sock, a Unix socket owned by root with group-write access for the docker group. A shell user outside that group gets a permission denial on connect, and the client reports the failure against the socket path rather than as a generic fault. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/permission-denied-docker-socket https://fixercode.com/software/docker/core/client-version-too-new Docker ships a versioned Engine API and lets client and daemon negotiate the highest version both understand. When negotiation is bypassed, for example through DOCKER_API_VERSION, or the gap predates the daemon's supported band, the daemon rejects the request with an explicit too-new or too-old line Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/client-version-too-new https://fixercode.com/software/docker/core/manifest-unknown A pull starts by requesting the image manifest, the document listing the image's layers and platforms. When the repository exists but the tag was never pushed, was deleted, or does not include the requesting platform, the registry answers with the manifest unknown condition and the daemon surfaces i Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/manifest-unknown https://fixercode.com/software/docker/core/pull-access-denied Registries deliberately give anonymous callers the same denial for a private repository and a nonexistent one, so the daemon's message lists both possibilities. The pull never starts; no layers download and the local image store stays untouched while credentials are sorted out. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/pull-access-denied https://fixercode.com/software/docker/core/unauthorized-authentication-required Registry APIs speak token auth: the client fetches a bearer token from an auth service and presents it with each request. When the token is absent, expired, or rejected, the registry returns an unauthorized condition with the authentication required body, and the daemon wraps it in its standard erro Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/unauthorized-authentication-required https://fixercode.com/software/docker/core/denied-requested-access This line is the registry's own denial body, usually attached to a push. Authentication succeeded, yet the account lacks write rights on the namespace, the namespace belongs to someone else, or the repository is read-only. The daemon passes the registry's wording through next to its own envelope. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/denied-requested-access https://fixercode.com/software/docker/core/toomanyrequests Docker Hub meters image pulls over a six-hour window: unauthenticated users draw from an allowance tied to their IPv4 address or IPv6 /64 subnet, authenticated Personal accounts from a per-user allowance, and paid tiers are unlimited. When a caller is over the limit, the registry answers the manifes Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/toomanyrequests https://fixercode.com/software/docker/core/x509-unknown-authority The daemon validates registry connections against the host trust store plus certificates under the Docker certificates directory. Self-signed or corporate-intercepted registries present a chain the client cannot verify, and the TLS layer rejects the handshake with the unknown-authority wording. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/x509-unknown-authority https://fixercode.com/software/docker/core/invalid-reference-format Image references follow a grammar: optional registry host, namespace path, repository name, tag, and digest. Uppercase letters in the repository part, stray characters, or an empty name after a host all fail validation locally, and the client rejects the reference before contacting any registry. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/invalid-reference-format https://fixercode.com/software/docker/core/port-is-already-allocated Publishing a container port asks the daemon to bind that port on the host. Docker tracks allocations across all containers, and when the requested port is already bound by another container the daemon refuses with the port-is-already-allocated wording inside its bind error. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/port-is-already-allocated https://fixercode.com/software/docker/core/address-already-in-use Underneath the allocator sits the actual system bind. When the address is taken by a process the daemon's bookkeeping does not track, the proxy component reports the kernel's address-already-in-use condition, usually wrapped in the userland proxy line. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/address-already-in-use https://fixercode.com/software/docker/core/driver-failed-external-connectivity When a container starts, the daemon asks the network driver to wire up published ports for the new endpoint. Failures at that step surface as the driver-failed-programming-external-connectivity line, typically followed by the underlying bind error that caused the wiring to fail. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/driver-failed-external-connectivity https://fixercode.com/software/docker/core/container-name-already-in-use Container names are unique across the daemon. Creating a new container with a name matching any existing container, running or stopped, is rejected with a conflict message that echoes the holder's ID. Auto-generated names avoid this by construction; explicit names collide on reuse. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/container-name-already-in-use https://fixercode.com/software/docker/core/no-space-left-on-device Images, container layers, volumes, and logs all live under the daemon's data root. When the backing filesystem hits its limit, layer extraction, log writes, and container creation abort with the kernel's no-space text, so the message reports the filesystem condition rather than a Docker-specific fau Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/no-space-left-on-device https://fixercode.com/software/docker/core/volume-in-use Named volumes persist independently of containers. The volume removal command refuses targets referenced by any container the daemon knows about, listing the referencing container IDs after the volume-is-in-use clause, because deleting a mounted volume would tear data out from live workloads. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/volume-in-use https://fixercode.com/software/docker/core/network-not-found User-defined networks live in the daemon's registry alongside its built-in peers. Connecting a container, inspecting, or removing a network by a name that was never created, or that a torn-down compose project already deleted, resolves to nothing and returns the not-found condition. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/network-not-found https://fixercode.com/software/docker/core/pool-overlaps Creating a network with an explicit subnet asks the address manager to reserve that range. When the range intersects any existing network's pool, including the daemon's default address pools, creation is refused with the pool-overlaps message and nothing is created. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/pool-overlaps https://fixercode.com/software/docker/core/no-such-container Container lookup accepts names and ID prefixes. A reference resolves to nothing after removal, after a typo, or against a different daemon context, and the failing command returns the no-such-container condition instead of operating on any workload. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/no-such-container https://fixercode.com/software/docker/core/container-is-not-running Exec sessions and attaches require a live process namespace to join. When the target container exited or was only created but never started, the daemon refuses the operation with the container-is-not-running condition and reports the container's actual state around it. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/container-is-not-running https://fixercode.com/software/docker/core/cannot-remove-a-running-container Container removal implies tearing down the writable layer and network attachments. The daemon refuses to do this for a running process unless the request explicitly forces it, returning the cannot-remove wording that points at the running state as the blocker. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/cannot-remove-a-running-container https://fixercode.com/software/docker/core/oci-runtime-create-failed Starting a container hands a prepared bundle to an OCI runtime such as runc. Failures inside that step, from invalid mount targets to blocked capabilities, surface as the oci-runtime-create-failed headline followed by the runtime's own diagnostic, appended after a type marker that often reads unknow Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/oci-runtime-create-failed https://fixercode.com/software/docker/core/exec-format-error Images bundle binaries for specific CPU architectures. Running an amd64 binary on an arm64 host, typically after pulling an image without an arm64 manifest entry, reaches the exec syscall, fails with the format error, and the runtime wraps the entrypoint failure in its start error. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/exec-format-error https://fixercode.com/software/docker/core/oci-runtime-exec-failed Exec into a live container asks the runtime to start an additional process inside the existing namespace. When the requested binary does not exist in the container filesystem, as with minimal distroless images lacking a shell, the runtime reports the exec failure with the not-found path detail. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/oci-runtime-exec-failed https://fixercode.com/software/docker/core/failed-to-solve BuildKit reports build failures in a solve envelope: the failed-to-solve headline carries the step identifier, the executed command, and the exit code. The envelope is diagnostic structure around an ordinary build-step failure rather than a builder malfunction. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/failed-to-solve https://fixercode.com/software/docker/core/dockerfile-not-found Every build names its Dockerfile, defaulting to a file of that name in the context root. When the file is absent, renamed, or sits in a subdirectory the flag does not point to, the solve step fails while reading the build definition with the no-such-file wording. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/dockerfile-not-found https://fixercode.com/software/docker/core/dependency-failed-to-start Compose supports ordering through dependency conditions, including waiting for a service to report healthy. When the dependency's health check never passes within its window, startup aborts with the dependency-failed-to-start line naming the container that stayed unhealthy. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/dependency-failed-to-start https://fixercode.com/software/docker/core/error-response-from-daemon Most Docker error output begins with this envelope: the CLI received an error response from the Engine API and prints it. The envelope itself carries no diagnosis; the registry, driver, or runtime text following it is the actual condition, from manifest unknown to network not found. Sat, 12 Sep 2026 00:00:00 GMT https://fixercode.com/software/docker/core/error-response-from-daemon https://fixercode.com/os/windows/system-errors/error-0x80070003 0x80070003 is the HRESULT wrapper around Win32 error 3, ERROR_PATH_NOT_FOUND, whose system text reads 'The system cannot find the path specified'. Where error 2 names a missing file, error 3 means the lookup failed earlier — one of the directories on the way to the target does not exist. Windows Upd Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x80070003 https://fixercode.com/os/windows/system-errors/error-0x8007000e An allocation the memory manager refuses returns 0x8007000E, the HRESULT form of Win32 error 14, ERROR_OUTOFMEMORY — 'Not enough storage is available to complete this operation'. The same value is registered as E_OUTOFMEMORY in Microsoft's common-HRESULT table, so COM callers and interop layers surf Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x8007000e https://fixercode.com/os/windows/system-errors/error-0x8007001f Hardware that stops answering mid-operation surfaces as 0x8007001F, Win32 error 31, ERROR_GEN_FAILURE — 'A device attached to the system is not functioning'. The upgrade resolution documentation carries the code into setup: 8007001F-0x4000D marks a general device failure during the second-boot phase Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x8007001f https://fixercode.com/os/windows/system-errors/error-0x80070032 A refusal that names the operation rather than any condition is 0x80070032, Win32 error 50, ERROR_NOT_SUPPORTED — 'The request is not supported'. Unlike an invalid parameter, nothing about the request is malformed; the receiver simply has no implementation behind it, which makes the code a statement Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x80070032 https://fixercode.com/os/windows/system-errors/error-0x8007007e When the loader walks an import list and one library never resolves, the failure is 0x8007007E, Win32 error 126, ERROR_MOD_NOT_FOUND — 'The specified module could not be found'. The upgrade documentation also records the code in servicing: WSUS environments that synced upgrade metadata before a requ Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x8007007e https://fixercode.com/os/windows/system-errors/error-0x80070103 Enumerations end quietly — 0x80070103 is the HRESULT for Win32 error 259, ERROR_NO_MORE_ITEMS, whose official text is simply 'No more data is available'. In Windows Update discussions the code is overwhelmingly reported on driver deliveries: the update surface tries to install a driver for a device Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x80070103 https://fixercode.com/os/windows/system-errors/error-0x8007025d Data that arrives inside a compressed stream and fails its structure checks stops an image apply with 0x8007025D, Win32 error 605, ERROR_BAD_COMPRESSION_BUFFER — 'The specified buffer contains ill-formed data'. The upgrade resolution tables pair the code with extend code 0x2000C and attribute it to Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x8007025d https://fixercode.com/os/windows/system-errors/error-0x8007042b A process that vanishes before finishing its work hands back 0x8007042B — Win32 error 1067, ERROR_PROCESS_ABORTED, whose system text reads 'The process terminated unexpectedly'. The upgrade resolution tables give the code its best-documented surface: 8007042B-0x4000D marks a second-boot failure duri Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x8007042b https://fixercode.com/os/windows/system-errors/error-0x8007045b Calls that arrive while Windows is already shutting down are declined with 0x8007045B, Win32 error 1115, ERROR_SHUTDOWN_IN_PROGRESS — 'A system shutdown is in progress'. The code is a boundary report: the caller reached the system, the request was understood, and the shutdown state forbade acting on Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x8007045b https://fixercode.com/os/windows/system-errors/error-0x80070570 A read that comes back structurally damaged raises 0x80070570, Win32 error 1392, ERROR_FILE_CORRUPT — 'The file or directory is corrupted and unreadable'. Windows Update troubleshooting lists the code under component store corruption, with the documented repair being DISM RestoreHealth followed by S Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x80070570 https://fixercode.com/os/windows/system-errors/error-0x800705aa Kernel bookkeeping has ceilings of its own, and exhausting them returns 0x800705AA, Win32 error 1450, ERROR_NO_SYSTEM_RESOURCES — 'Insufficient system resources exist to complete the requested service'. The message deliberately avoids the word memory: the shortage sits in fixed-size kernel pools and Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x800705aa https://fixercode.com/os/windows/system-errors/error-0x800706ba Remote procedure calls begin with a rendezvous, and 0x800706BA, Win32 error 1722, RPC_S_SERVER_UNAVAILABLE — 'The RPC server is unavailable' — means that rendezvous never happened. Management tooling that leans on DCOM and WMI makes the code a common cross-machine diagnostic: the local caller works, Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x800706ba https://fixercode.com/os/windows/system-errors/error-0x800706be The code 0x800706BE, Win32 error 1726, RPC_S_CALL_FAILED — 'The remote procedure call failed' — describes a delivered call with a dead execution. The endpoint answered, the method was invoked, and the failure happened inside the server process, which separates it from 1722, where nothing was ever re Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x800706be https://fixercode.com/os/windows/system-errors/error-0x80071392 Two objects cannot hold one identity, and a creation that tries anyway fails with 0x80071392, Win32 error 5010, ERROR_OBJECT_ALREADY_EXISTS — 'The object already exists'. The constant originates in the cluster resource API family — its message speaks of resources and groups — and servicing or manage Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x80071392 https://fixercode.com/os/windows/system-errors/error-0x8007139f State machines accept only certain transitions, and a request issued from the wrong state is refused with 0x8007139F, Win32 error 5023, ERROR_INVALID_STATE — the official message reads 'The group or resource is not in the correct state to perform the requested operation'. The refusal is about orderi Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x8007139f https://fixercode.com/os/windows/system-errors/error-0x80072efd A TCP connect that dies before the first response byte — refused, unroutable, or silently filtered — produces 0x80072EFD, the HRESULT form of WinINet error 12029, ERROR_INTERNET_CANNOT_CONNECT: 'The attempt to connect to the server failed'. Windows Update troubleshooting groups the code with 0x80072 Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x80072efd https://fixercode.com/os/windows/system-errors/error-0x80072ee7 Before any HTTP exchange, a hostname has to become an address; when that translation fails, WinINet reports 0x80072EE7, error 12007, ERROR_INTERNET_NAME_NOT_RESOLVED — 'The server name could not be resolved'. The failure happens ahead of connecting entirely, so no server ever sees the request and no Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x80072ee7 https://fixercode.com/os/windows/system-errors/error-0x80072efe Transfers that die mid-flight — after the handshake, during the payload — end with 0x80072EFE, the HRESULT of WinINet error 12030, ERROR_INTERNET_CONNECTION_ABORTED: 'The connection with the server has been terminated'. Windows Update documentation gives the code a specific owner: BITS, which surfac Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x80072efe https://fixercode.com/os/windows/system-errors/error-0x800b0109 Certificate chains can verify cleanly and still be refused at the last step: 0x800B0109, CERT_E_UNTRUSTEDROOT, fires when the chain terminates in a root certificate the trust provider does not trust. Microsoft's DirectAccess troubleshooting documents the code for IP-HTTPS connections, and the same f Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x800b0109 https://fixercode.com/os/windows/system-errors/error-0x80244018 Inside the Windows Update protocol talker, an HTTP 403 from the update source is re-raised as 0x80244018, WU_E_PT_HTTP_STATUS_FORBIDDEN. Microsoft's error reference defines it — 'Same as HTTP status 403 - server understood the request but declined to fulfill it' — and the upgrade documentation pairs Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x80244018 https://fixercode.com/os/windows/system-errors/error-0x80244019 An HTTP 404 returned to the Windows Update agent is re-raised as 0x80244019, WU_E_PT_HTTP_STATUS_NOT_FOUND — 'Same as HTTP status 404 - the server can't find the requested URI (Uniform Resource Identifier)'. Microsoft's error reference defines the code in the protocol-talker family, and in managed e Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x80244019 https://fixercode.com/os/windows/system-errors/error-0x800f0906 Optional features such as .NET Framework 3.5 are not stored on disk by default, and when servicing cannot fetch their payload the request fails with 0x800F0906. Microsoft's .NET Framework 3.5 installation guidance records the message — 'The source files could not be downloaded' — and attributes the Sun, 06 Sep 2026 00:00:00 GMT https://fixercode.com/os/windows/system-errors/error-0x800f0906