Docker troubleshooting

Diagnose health checks, proxy responses, stale assets, and container permission errors.

Browser only

The health check fails

Run docker logs dcmage. Confirm that port 8080 is free and that both temporary filesystems from the deployment example are present.

The browser cannot decode images

Inspect the proxy response for .wasm files. The proxy must return application/wasm without content transformation.

A route returns the proxy 404 page

Forward the complete root path to the container. Do not add a URL prefix or implement SPA routing in the external proxy.

The page shows old code

Remove any immutable proxy cache rule for index.html, then reload the browser tab. Hashed files under /assets/ can be cached immutably; index.html cannot.

Browser features fail on a remote host

Use HTTPS with a valid certificate. Check the browser console for messages about blocked secure-context features.

NGINX reports permission errors

Use the documented temporary filesystems. Do not change the container from numeric user 101.

A former fixture URL shows the application shell

Do not rewrite .dcm, .dicom, or fixture-directory 404 responses in the external proxy.

Return to Deploy with Docker.