Navigator
Notes & Troubleshooting
Common issues and design notes for the DMC Navigator on-prem workflow.
- Clean errors by design. Errors print a single line. For full tracebacks
while diagnosing, set
DMC_NAV_DEBUG=1in.env. - License is hardware-bound. If you move to a different machine/VM, re-run
navigator machine-idthere and request a new license — the old one will report a hardware-fingerprint mismatch. - "No license found". Install one with
navigator update-license, or check thatDMC_NAV_LICENSE_FILEin.envpoints at it. - Permissions on
./runs. The container runs as your UID/GID (recorded in.envat install) so generated files are owned by you. - AWS
AccessDeniedduring login. Confirm that the active profile contains the customer source credentials supplied by Deep-MedChem. Do not add ECR permissions to that user; it only needs permission to assumenavigator-onprem-pull. - arm64 host. The current release is
linux/amd64only. Use a supported x86_64 Linux host for production rather than relying on emulation. - Updating the image. Run
navigator update. It fetches the configured tag in.env(DMC_NAV_IMAGE_TAG) and reports whether the local image changed. Existing runs, inputs, and the installed license remain in place. - Existing
latestinstalls. ChangeDMC_NAV_IMAGE_TAG=latesttoDMC_NAV_IMAGE_TAG=stablein.envonce, then runnavigator update.