Docker & Compose
Install Docker with the Compose plugin on the host where you plan to run the services.
GET STARTED / DOCKER HUB
Install Sysadmin Anywhere 5.0.0 from ready-made Docker Hub images. Download only the deployment configuration from this site; Docker Compose fetches the application and supporting images. No source checkout or build is required.
BEFORE YOU BEGIN
The application connects to your directory and supporting services. Gather these details before starting the containers.
Install Docker with the Compose plugin on the host where you plan to run the services.
Know the domain controller hostname, LDAP port, and accounts used for login and inventory scans.
Prepare unique database, Vault, JWT, and n8n secrets. Review network ports and persistent storage.
THE PATH TO FIRST LOGIN
The four product images are published on Docker Hub with the 5.0.0 tag. Run these commands in the extracted configuration directory.
Download and extract the configuration bundle above. It contains no application source code. Open a terminal in its docker/prod directory.
cd docker/prodCopy .env.example to .env. Set the LDAP, inventory, WEF, and n8n values, and replace every example password and token before starting. Keep .env private.
cp .env.example .envRun the pull command in docker/prod. Compose downloads sysadminanywhere/sysadminanywhere, sysadminanywhere/directory, sysadminanywhere/inventory, and sysadminanywhere/incident, along with the database and supporting images.
docker compose pullStart the application and its supporting services. Check the container logs if a service does not become ready.
docker compose up -dOpen http://localhost:8080/login from the host, sign in with your Active Directory account, and ask an administrator to review /settings/dependencies if a service is unavailable.
http://localhost:8080/loginBEFORE PRODUCTION
The supplied Compose file pins the four Sysadmin Anywhere images to 5.0.0. PostgreSQL uses version 17, while Vault and n8n use floating tags. The Vault service runs in development mode; replace it with a production-ready configuration before deploying to production.
Replace every example secret, review access and exposed ports, and configure TLS and certificate trust for your environment. Keep your .env file private.
WHAT'S NEXT?