Navigator

Notes & Troubleshooting

Common issues and design notes for the DMC Navigator on-prem workflow.

Suggest an edit
  • Clean errors by design. Errors print a single line. For full tracebacks while diagnosing, set DMC_NAV_DEBUG=1 in .env.
  • License is hardware-bound. If you move to a different machine/VM, re-run navigator machine-id there 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 that DMC_NAV_LICENSE_FILE in .env points at it.
  • Permissions on ./runs. The container runs as your UID/GID (recorded in .env at install) so generated files are owned by you.
  • AWS AccessDenied during 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 assume navigator-onprem-pull.
  • arm64 host. The current release is linux/amd64 only. 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 latest installs. Change DMC_NAV_IMAGE_TAG=latest to DMC_NAV_IMAGE_TAG=stable in .env once, then run navigator update.