No Update Offered
Symptom: The Atlas Status page in Dermi Atlas Manager shows neither an Atlas Update card nor an Updates card, although a newer release exists.
Solutions:
- One release at a time: Updates install one release after another. After an update finishes, Atlas Manager offers the next release, if there is one.
- Connection: Checking for updates needs an internet connection and Docker running. Check that a firewall or proxy does not block
releases.dermi.ai on port 443, then open the Atlas Status page again.
- Atlas Manager first: When an Atlas Manager update is also available, the card shows Step 1: Update Atlas Manager and Step 2: Update Atlas, and Begin Atlas Update becomes available once Atlas Manager has been updated.
- License: "Available once the license is active." means the license needs attention; see Troubleshooting Licensing and Subscription Issues.
Atlas Manager Update Required
Symptom: The Requirements step of the update shows Atlas Manager Update Required or Incompatible Atlas Manager Version.
Solutions:
- Select Download Update in the box, then Restart and Install, or download the latest Atlas Manager from the Dermi Portal. Start the Atlas update again afterward.
- On macOS, a system prompt may ask to allow Dermi Atlas Manager to access files or data from other apps during the update. Select Allow.
- If the Atlas Manager row reads "Atlas Manager X is installed; this release needs Y or newer.", select Check Again in the box. If the box has no Check Again button, select Clear Cache on the Administration page, then quit and reopen Atlas Manager.
- If the box reads Incompatible Atlas Manager Version, or the Atlas Manager row reads "Atlas Manager X is installed; this release supports up to Y.", contact Dermi support.
Update Stops Before Anything Changes
Symptom: The update ends under "Could not update Atlas" with one of the messages below. Atlas stays on the installed version, unchanged.
- "This computer does not meet the requirements." followed by the unmet requirements. See Troubleshooting Docker and System Requirements.
- "The update is not compatible with this installation. Contact support." Contact Dermi support.
- "Docker could not read the release files. Run the update again." Quit and reopen Docker Desktop, then run the update again.
- "Atlas X is no longer available for download. Contact support." Contact Dermi support.
- "The download of Atlas X could not be confirmed. Run the update again." Check the internet connection, then run the update again.
- A license message, such as "Dermi could not be reached. Check the internet connection and try again." The update downloads the new version through Dermi, so it needs an active license and a connection; address what the message or the License Status card on the Atlas Status page names, then run the update again.
- "Could not load the deployment environment. Contact support." Contact Dermi support.
- "The last restore did not finish, so Atlas holds incomplete data. Restore a backup first." See Troubleshooting Backup and Restore Issues.
Backup or Disk Space Check Fails
Symptom: An update whose Options step reads "This update requires a backup." stops while creating or checking that backup. Atlas stays on the installed version and runs as it did before.
- A backup message, such as "Not enough free space for the backup: X needed, Y available." Free the space the message names, then run the update again.
- "Some image paths are too long for Windows, so the backup was not made." Turn on long paths in Windows, quit and reopen Atlas Manager, then run the update again.
- "The backup created before the update is missing. Run the update again." or a message beginning "The backup could not be verified:". Run the update again, which creates and checks a new backup. If the same message returns, send diagnostics to Dermi support.
- "The Docker disk has" or "The drive that holds the Docker data has" followed by the space needed. Apply the remedy at the end of the message, then run the update again.
Message Contains "Atlas was returned to version"
Symptom: An update that required a backup ends under "Could not update Atlas" with the reason it stopped, followed by "Atlas was returned to version" and the version installed before the update.
Solutions:
- Atlas is back on that version, with its data as it was before the update. Address the reason the message names first, for example the internet connection or a download message such as "Could not download" followed by a component name, then run the update again from the Atlas Status page. The new run creates a new backup.
- If the reason ends with "Docker rejected the image.", quit and reopen Docker Desktop, then run the update again.
- If the message continues with "but its data was not found in Docker. Restore a backup in Backup Management.", restore the backup labeled Pre-Update in Backup Management.
- If "Atlas was returned to version" is followed by another reason, Atlas did not start. Address that reason, then select Restart in the Atlas Control card, or Start when the card shows Atlas stopped.
Message Begins "Atlas could not be returned to version"
Symptom: The update ends with "Atlas could not be returned to version", a reason, and an instruction such as "Run the update again."
Solution: Address the reason first, for example the internet connection, Docker, free disk space, or "The Atlas Manager data folder could not be written to.", which asks to check the permissions of that folder. Then select Retry and start the update again. That run returns Atlas to the version named in the message, as described in the next section. If the earlier version still cannot be downloaded on a working internet connection, contact Dermi support before trying again.
"The last update did not finish."
Symptom: An update that required a backup stopped part way, for example because the computer restarted, Docker stopped, or Atlas Manager was closed. Start and Restart are refused with "The last update did not finish. Run the update again.", and creating a backup, restoring in Backup Management, and uninstalling are refused with messages that begin the same way.
Solutions:
- Select Finish Atlas Update (Begin Atlas Update on an earlier Atlas Manager) on the Atlas Status page. The Options step lists "The last update did not finish" and the version installed before the update.
- Select Start Update. With an internet connection, Atlas Manager returns Atlas to that version, even when the newer version was already installed. The run ends under "Could not update Atlas" with "The last update did not finish. Atlas was returned to version" and the version.
- Select Retry to run the update again from the beginning, with a new backup. The update is downloaded again.
Two variants need a different step. "The last update did not finish. Contact support." is sent to Dermi support. "The last update did not finish. Restore a backup to install Atlas." is resolved with the Restore Backup option of the installation wizard.
Update Ends with "Select Restart" or Fails Without a Required Backup
Symptom: An update ends under "Could not update Atlas" with a reason followed by "Select Restart in the Atlas Control card, or Start when Atlas is stopped.", or an update that did not require a backup ends with a reason followed by "Run the update again." or stops without a message because Atlas Manager was closed or the computer restarted.
Solutions:
- Address the reason the message names, if any, then run the update again from the Atlas Status page; the message may begin with "No internet connection." when the connection dropped during the update. The data of Atlas is untouched, and this is also the first step when no message was shown. If the Atlas Status page already shows the new version, select Restart in the Atlas Control card, or Start when the card shows Atlas stopped.
- If the message ends with "Select Restart in the Atlas Control card, or Start when Atlas is stopped.", the new version is installed but did not start. Select Restart in the Atlas Control card, or Start when the card shows Atlas stopped. If that fails, address the cause its message names, if any, then select it again.
- Only if the update fails again the same way, select Begin Uninstall on the Administration page with Create Backup left on, then install Atlas with the Restore Backup option and choose the backup labeled Pre-Update. Backing Up and Restoring Dermi Atlas Professional describes the restore. If the backup of the uninstall fails, or no Pre-Update backup exists, contact Dermi support rather than turning Create Backup off.
Running the update again is also the first step when an earlier version of Atlas Manager ends the same failure with "Uninstall Atlas, then restore the backup created before the update from the installer." or "No backup was created before this update."
Related Articles
- Troubleshooting Atlas Installation and Start Issues for Atlas Manager closed during an operation
- Troubleshooting Dermi Atlas for sending diagnostics to Dermi support