Problem family
Servers troubleshooting
These records share a system family, but each page stays scoped to one symptom or failure state.
VERIFIED
Docker bind mount permission deniedDocker bind mount permission denied? Verify the host path, container user and mount type before loosening permissions or rebuilding the image. This source-reviewed guide keeps the next action tied to the evidence you can collect safely.
Reviewed Sep 26, 2026Public launch · Docker
VERIFIEDCannot connect to the Docker daemonDocker documents two primary causes for “Cannot connect to the Docker daemon”: the daemon is not running, or the client is pointed at another unreachable daemon. On Linux, local Unix-socket permissions can also prevent a non-root user from connecting even when dockerd is healthy.
Reviewed Sep 26, 2026Editorial hold · Docker
VERIFIEDDocker Compose environment variables are not loadingCompose variable substitution and a container’s runtime environment are related but not identical. A variable can be available to Compose without being passed into a service unless the service configuration explicitly includes it.
Reviewed Oct 2, 2026Public launch · Docker
VERIFIEDDocker Compose networking is not workingThis source-reviewed guide separates local device and application checks from account, carrier, network, service and dependency failures. It keeps recovery steps bounded, preserves useful evidence and explains when broader repair or vendor escalation is the safer next step.
Reviewed Oct 5, 2026Public launch · Docker
VERIFIEDDocker Compose production deployment is not workingThis source-reviewed guide separates local device and application checks from account, carrier, network, service and dependency failures. It keeps recovery steps bounded, preserves useful evidence and explains when broader repair or vendor escalation is the safer next step.
Reviewed Oct 5, 2026Public launch · Docker
VERIFIEDDocker Compose restart is not applying changesThis source-reviewed guide separates local device and application checks from account, carrier, network, service and dependency failures. It keeps recovery steps bounded, preserves useful evidence and explains when broader repair or vendor escalation is the safer next step.
Reviewed Oct 5, 2026Public launch · Docker
VERIFIEDDocker Compose starts a service before its dependency is readyThis source-reviewed guide separates local device and application checks from account, carrier, network, service and dependency failures. It keeps recovery steps bounded, preserves useful evidence and explains when broader repair or vendor escalation is the safer next step.
Reviewed Oct 5, 2026Public launch · Docker
VERIFIEDDocker Compose service is not startingThis source-reviewed guide separates local device and application checks from account, carrier, network, service and dependency failures. It keeps recovery steps bounded, preserves useful evidence and explains when broader repair or vendor escalation is the safer next step.
Reviewed Oct 5, 2026Public launch · Docker
VERIFIEDDocker container DNS resolution not workingDocker containers normally inherit or proxy DNS based on the network they use. Default-bridge containers receive resolver settings derived from the host, while custom networks use Docker’s embedded DNS. Loopback resolvers such as 127.0.0.1 on the host are a common mismatch because that address means the container itself inside its network namespace.
Reviewed Sep 26, 2026Editorial hold · Docker
VERIFIEDDocker container exited with code 137Treat exit code 137 as evidence that the process received SIGKILL, not as proof that one specific component failed. Preserve state and logs, then determine whether an OOM event, a manual kill, a daemon restart or another external action occurred. This source-reviewed guide keeps the next step tied to the evidence you can collect safely.
Reviewed Sep 25, 2026Public launch · Docker
VERIFIEDDocker container keeps restarting in a loopA Docker container that repeatedly returns to a running/restarting state can be caused by its main process exiting while a restart policy relaunches it. First inspect the container state, restart count and policy; also note that Docker only activates a restart policy after the container has started successfully for at least 10 seconds.
Reviewed Sep 26, 2026Public launch · Docker
VERIFIEDDocker container logs are missing or emptydocker logs exposes output available through the container logging configuration. Missing output is evidence to inspect process destination and logging driver before deleting containers or recreating a volume.
Reviewed Oct 2, 2026Public launch · Docker
VERIFIEDDocker container is unhealthyDocker marks a container unhealthy after the configured number of consecutive failed health checks. The healthcheck command and its timing determine whether the failure is an application readiness issue, bad check or dependency path.
Reviewed Oct 2, 2026Public launch · Docker
VERIFIEDDocker image pull failedDocker image pull failed is best handled by preserving the exact symptom first, identifying whether the failure follows a local device, account, network, carrier, service or dependency branch, and then applying only the safe documented recovery step. This guide explains what to verify before escalation.
Reviewed Oct 20, 2026Public launch · Docker
VERIFIEDDocker image pull times out or cannot connectDocker image pull times out? Confirm registry reachability, DNS, proxy and the exact image reference before changing daemon settings or retrying broadly. This source-reviewed guide keeps the next action tied to the evidence you can collect safely.
Reviewed Sep 26, 2026Public launch · Docker
VERIFIEDDocker: no space left on deviceDocker can consume substantial storage through images, stopped containers, build cache and volumes. A no-space error may also come from the host filesystem or inode exhaustion. Docker provides docker system df to measure daemon usage and conservative prune commands that only remove categories you explicitly choose.
Reviewed Sep 26, 2026Editorial hold · Docker
VERIFIEDDocker port is already allocatedDocker port is already allocated? Identify the process or container bound to the host port, then choose a targeted stop or a different published port. This source-reviewed guide keeps the next action tied to the evidence you can collect safely.
Reviewed Sep 26, 2026Public launch · Docker
VERIFIEDDocker published port is not reachableDocker containers are isolated by default, so a service is not reachable from outside the host until the correct container port is published with `-p` or `--publish`; a Dockerfile `EXPOSE` instruction alone does not create a host mapping. A localhost-only host bind can also intentionally prevent remote access.
Reviewed Sep 26, 2026Editorial hold · Docker
VERIFIEDDocker pull access denied or repository does not existVerify the exact image reference first, including registry hostname, namespace and tag. Then authenticate only to the intended registry and confirm the account or token is permitted to pull that private repository. This source-reviewed guide keeps the next step tied to the evidence you can collect safely.
Reviewed Sep 25, 2026Public launch · Docker
VERIFIEDDocker volume permission deniedDocker volume permission denied is best handled by preserving the exact symptom first, identifying whether the failure follows a local device, account, network, carrier, service or dependency branch, and then applying only the safe documented recovery step. This guide explains what to verify before escalation.
Reviewed Oct 20, 2026Public launch · Docker
VERIFIEDProxmox backup task failed: read the task log firstStart with the full task log and the first concrete error, not the final TASK ERROR line. Separate storage reachability, available capacity, guest-specific failure and transport/authentication evidence before changing backup settings. This source-reviewed guide keeps the next step tied to the evidence you can collect safely.
Reviewed Sep 25, 2026Public launch · Proxmox VE
VERIFIEDProxmox cluster has no quorumProxmox cluster has no quorum? Confirm node and corosync reachability before changing services, votes or cluster configuration on the affected host. This source-reviewed guide keeps the next action tied to the evidence you can collect safely.
Reviewed Sep 26, 2026Public launch · Proxmox VE
VERIFIEDProxmox migration failedProxmox migration failed? Read the first task-log error, then separate guest, storage, network and CPU compatibility causes before retrying. This source-reviewed guide keeps the next action tied to the evidence you can collect safely.
Reviewed Sep 26, 2026Public launch · Proxmox VE
VERIFIEDProxmox node shows offlineAn offline node can be a host reachability fault, a management-service problem or a cluster communication/quorum condition. Guest recovery actions must follow the actual cluster state to avoid conflicting changes.
Reviewed Oct 2, 2026Public launch · Proxmox VE
VERIFIEDProxmox storage is fullProxmox storage is full? Stop new writes, identify the affected storage and free or extend capacity safely before guest I/O errors cause wider damage. This source-reviewed guide keeps the next action tied to the evidence you can collect safely.
Reviewed Sep 26, 2026Public launch · Proxmox VE
VERIFIEDProxmox storage is not availableProxmox storage is not available? Confirm the exact storage ID, node scope, mount state and capacity before editing storage configuration or guest disks. This source-reviewed guide keeps the next action tied to the evidence you can collect safely.
Reviewed Sep 26, 2026Public launch · Proxmox VE
VERIFIEDProxmox VM has no network or internet accessA Proxmox VE guest normally reaches the physical network through a Linux bridge such as vmbr0. If the VM has no network, verify the VM NIC, bridge attachment, host bridge uplink and guest IP configuration in that order.
Reviewed Sep 6, 2026Editorial hold · Proxmox VE
VERIFIEDProxmox VM or container will not startRead the failed start task log before changing guest hardware, storage or the host. First separate a guest-only failure from a node-wide issue and identify whether the log points to storage, a lock, a resource limit, configuration or an external dependency. This source-reviewed guide keeps the next step tied to the evidence you can collect safely.
Reviewed Sep 25, 2026Public launch · Proxmox VE
VERIFIEDProxmox web interface is not reachableThe Proxmox GUI depends on node reachability, network configuration and the API daemon path. A browser failure does not prove that guests or storage are down, so keep the first checks narrow.
Reviewed Oct 2, 2026Public launch · Proxmox VE