About the Docker image
What the container includes, how the browser handles DICOM data, and what the image does not provide.
Browser only
The image serves the static dcmage browser application for linux/amd64 and linux/arm64.
It is not a DICOM server, PACS, DICOMweb endpoint, API, or database. Users select DICOM files through the browser. The browser reads those files into browser memory. The container does not receive, store, index, or back up the files.
The image contains no test DICOM data. The Docker build disables feedback controls and feedback network paths. The build obfuscates application JavaScript to increase inspection effort. Obfuscation is not a security boundary.
The image does not make a deployment HIPAA, GDPR, MDR, or medical-device compliant.
Runtime details
| Item | Value |
|---|---|
| Image | ghcr.io/kiwiprojekt/dcmage-release |
| Platforms | linux/amd64, linux/arm64 |
| Container port | 8080/tcp |
| Health path | /healthz |
| User | Numeric user 101 |
| Filesystem | Read-only, with temporary filesystems for NGINX |
| URL base | Root path / only |
| Feedback | Disabled at build time |
| Application storage | Browser memory and browser-managed preferences only |
Use a current Chromium, Firefox, or Safari browser with WebAssembly and WebGL 2 support. Imaging work uses the browser’s RAM and GPU. The static server needs little memory by comparison. Start with 64 MiB for the container and monitor the deployment.
Image tags
The latest tag points to the newest published container image. See the
GitHub container package
for the available version tags.
Use latest for an initial deployment.
For production, select a published version tag from that page.
Use its digest for a fully repeatable deployment.
Next: Deploy with Docker.