/
Resolve Docker-related problems affecting Dermi Atlas Professional, including Docker not detected, Docker Desktop startup issues, insufficient resources, and ARM64 emulation errors.
Symptom: The Dermi Atlas Manager requirements check shows the Docker row as Not detected, with the message that the Docker client is not available.
Solutions:
docker group (sudo usermod -aG docker $USER).28.0.0 or newer. If the requirements check reports that the installed version is too old, upgrade Docker and re-run the check.Symptom: Docker hangs on "Starting..."
Solutions:
wsl --shutdown in PowerShell (Admin) and restart Docker.Symptom: Dermi Atlas Professional runs slowly or crashes.
Solution:
The System Memory requirements check reflects total host RAM, not the Docker Desktop allocation. Increasing the Docker Desktop memory allocation affects runtime performance but does not change what the check reports. For full requirements, see System Requirements for Dermi Atlas.
Increasing the memory available to Docker helps only when the host or Docker itself is memory-constrained. The Atlas Vision service that performs image alignment is capped at 2GB by the deployed stack, so a larger allocation does not raise that ceiling.
Symptom: On a Windows on ARM (ARM64) computer, the Network Gateway container logs io_setup() failed (38: Function not implemented), and Dermi Atlas Professional does not run reliably.
Cause: Dermi Atlas Professional container images are published for amd64 (x64) only. On Windows on ARM, Docker Desktop runs amd64 images through QEMU emulation, which does not implement the asynchronous I/O system call the Network Gateway requires. Running Dermi Atlas Professional under emulation is not supported, even when individual containers appear to start.
Solution:
Native ARM64 container images are not provided. For the supported platforms, see Hardware and Software Requirements.
Your feedback helps us improve our documentation
Contact our support team for personalized help