Docker compose proxy versus origin split response

When this happens

Use this when a cdn, load balancer, reverse proxy, or waf sits in front of the service. Do not stop at the screen message; validate whether the edge/proxy or the origin server creates the failure first.

Symptom checklist

• compose appears repeatedly in the Docker UI or logs.
• logs, exit code, volume, network, port bind differs between successful and failed requests.
• The issue appears only after separating image issue from runtime environment issue.
• It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

• compose specifically changes the investigation surface for Docker: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• A stopped or running container still owns the host port mapping.
• docker compose project names create different network and service names than expected.
• The container sees a different env file than the shell used to start it.
• A bind-mounted volume has host ownership that the container user cannot write.
• Healthcheck state hides the real process log.
• For the proxy versus origin split case, the first useful clue is whether the edge/proxy or the origin server creates the failure.

First 1-minute checks

1. Write down the first failure time, latest change, affected user, path, and object ID.
2. Compare logs, exit code, volume, network, port bind for success and failure in the same window.
3. Test the hypothesis: Docker failure caused by occupied host port, compose network naming, stale container, env file drift, or volume ownership.
4. Classify this as proxy versus origin split: whether the edge/proxy or the origin server creates the failure.
5. Capture current values before changing configuration.

First evidence

Treat compose as a proxy versus origin split case. First collect evidence for whether the edge/proxy or the origin server creates the failure.

Output examples

Normal output

Direct origin and routed proxy return equivalent status and headers.

Failing output

Origin succeeds but proxy fails, or proxy succeeds while direct origin exposes the real backend error.

Output-to-action branches

• A CDN, load balancer, reverse proxy, or WAF sits in front of the service.
  Test direct origin and routed traffic separately, then change only the layer that differs.
• The working and failing outputs differ.
  Act on the differing layer first: For compose, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Command output is normal but users still fail.
  Separate browser cache, cookies, permissions, and network location before declaring it fixed.

Do not do this

• Do not assume the CDN error code is the application root cause.
• Do not change multiple layers before identifying the failing layer.
• Do not delete production data, grant broad permissions, or disable security controls as a first response.

Evidence quality

Auto-generated operator draft: includes issue-specific causes, commands, output branches, and unsafe-action warnings. Official-source links and real incident validation are queued for enrichment.

Commands to run first

grep -R "compose" ./logs

docker ps -a

docker logs CONTAINER --tail 200

docker inspect CONTAINER

docker compose config

docker ps -a

docker compose config

docker compose logs --tail=200

ss -ltnp | grep ':PORT'

curl -Iv https://example.com --resolve example.com:443:ORIGIN_IP

Fix order

1. Record the full compose message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for Docker failure caused by occupied host port, compose network naming, stale container, env file drift, or volume ownership.
3. Compare the failing case with a successful case before editing settings.
4. If this is the proxy versus origin split branch, Test direct origin and routed traffic separately, then change only the layer that differs.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For compose, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• List containers and host listeners before changing ports.
• Use a stable compose project name and inspect generated networks.
• Print the resolved compose config to verify env files and mounts.
• Fix host volume ownership or run the process as the intended UID.
• Read container logs and healthcheck output before rebuilding images.
• For the proxy versus origin split branch, Test direct origin and routed traffic separately, then change only the layer that differs.

Evidence links

• Docker troubleshooting official
• Docker Compose reference official

Verification metadata

• operator-draft
• official-reference-linked
• 2026-07-23

Update queue

• Review cadence
  weekly-source-review
• Next enrichment
  Add one official-source check and one real output example for Docker compose.

Environment-specific checks

• Shared hosting, proxies, VPNs, or CDN layers can change image issue from runtime environment issue results.
• Do not trust only the Docker UI; compare command output.
• Japanese hosting panels may show completion before DNS or SSL fully propagates.
• Test from both office and external networks.

Prevent it next time

• Store normal examples for logs, exit code, volume, network, port bind.
• Add volume permissions, port conflicts, image tag, healthcheck to the release checklist.
• Keep recurring errors in the same note format.
• Split alerts by error rate, latency, certificates, disk, and permission changes.

Related notes

• Docker container exited 137
• Docker port already allocated fix note
• Docker docker.sock fix note
• Docker port already allocated fix note 2
• Docker docker.sock fix note 2
• Docker port already allocated fix note 3
• Docker docker.sock fix note 3
• Docker port already allocated fix note 4