Installation Stops with "Could not install Atlas"
Symptom: After the Requirements step, the progress card of the Dermi Atlas Manager installer reads "Could not install Atlas", with a message below it.
Solutions:
- "Could not download" followed by a component name. Atlas Manager could not download that part of Atlas from Dermi. Check the internet connection of the host computer, turn off any VPN during the installation, and check that a firewall or proxy does not block
releases.dermi.ai on port 443. A message ending in "the signature did not match." means the download arrived damaged; run the installation again.
- "Could not load" followed by a component name and "Docker rejected the image." Docker could not take in the downloaded component, for example because Docker stopped or is not responding, or its disk is full. Quit Docker Desktop fully and reopen it, or restart the Docker service on Linux, and check the Docker disk space as described in Troubleshooting Docker and System Requirements. Then run the installation again.
- "The Docker disk has" or "The drive that holds the Docker data has". The message states the space needed and the remedy; apply it, then run the installation again.
Retry returns the wizard to the Requirements step, from where the installation runs again from the beginning.
First Start Fails
Symptom: The installation or the first Start ends with "Could not start Atlas services" followed by a reason.
Two Atlas components are downloaded from Docker Hub the first time Atlas starts. A firewall, proxy, or VPN that blocks Docker Hub stops that first start. Allow Docker Hub, or turn off the VPN, and select Start in the Atlas Control card on the Atlas Status page. Later starts use the downloaded components and need no connection to Docker Hub.
Atlas Does Not Start or Reports Errors
Symptom: The Atlas Control card reads "Could not start Atlas", or the Container Status card on the Atlas Status page reads "Some containers have errors" or a count such as "7/9 containers running", with rows marked Stopped, Error, or Unhealthy.
Solutions:
- Restart: Select Restart in the Atlas Control card.
- Slow start: "Atlas started but did not reach full health within the expected time. Check the container status for details." means Atlas started but some parts were not ready in time. Wait a few minutes and check the Container Status card again; if rows stay Unhealthy or Starting, select Restart.
- Ports: Start and Restart move Atlas to another port when a default port is busy and, on Windows, update the firewall rules, which needs administrator rights. The ports in use appear on the Atlas Access card; see Firewall Configuration for Dermi Atlas Professional.
- Memory and disk space: Check that the computer meets the requirements in System Requirements.
- Still failing: Select Support beside the failure, then Send Diagnostics, as described in Troubleshooting Dermi Atlas.
Start is refused with a message when an earlier operation did not finish:
- "The last update did not finish. Run the update again." See Troubleshooting System Update Issues.
- "The last restore did not finish, so Atlas holds incomplete data. Restore a backup first." See Troubleshooting Backup and Restore Issues.
Atlas Manager Closed During an Operation
Symptom: Closing Atlas Manager shows "Close Atlas Manager?" with "An operation is in progress. Closing now can leave Atlas in an incomplete state."
Select Cancel and let the operation finish. The installer also asks to keep Atlas Manager open and not to restart the computer while it works.
If Atlas Manager was closed anyway, or the computer restarted, the next launch picks up as follows:
- Installation: Atlas Manager opens the installer again. Run the installation again from the beginning.
- Update: Atlas Manager reports "The last update did not finish."; see Troubleshooting System Update Issues.
- Backup or restore: Atlas Manager shows a Service Recovery chip while it puts Atlas back in order; see Troubleshooting Backup and Restore Issues.
Related Articles
- Deploying Dermi Atlas Professional for the installation steps in Atlas Manager
- Troubleshooting Docker and System Requirements for problems at the Requirements step