Running Docker Images

Running Rundeck in Docker offers several advantages, including portability across different environments, consistency in application behavior, isolation from other applications, scalability for handling increased workloads, and simplified deployment and management processes. Docker's containerization enables the packaging of Rundeck and its dependencies into a single container, allowing for easy distribution, deployment, and scaling. This approach ensures that Rundeck operates consistently, reduces compatibility issues, and provides flexibility for customers to run Rundeck in their preferred environments.

Full usage information can be found on the Docker configuration page.

Warning

It's not advisable to deploy images to production directly from a public repository, such as Dockerhub.
Build a derived image and store in your private repository instead.

Tips

See the Docker Configuration Reference for
the full set of configuration options.

Open Source Rundeck

rundeck/rundeck:5.8.0

docker run --name some-rundeck -p 4440:4440 -v data:/home/rundeck/server/data rundeck/rundeck:5.8.0

Runbook Automation Self-Hosted

rundeckpro/enterprise:5.8.0
The following example invocation will require an accessible MySQL instance
with a database, user, and the required privileges setup:

docker run \
    --name some-rundeck \
    -v data:/home/rundeck/server/data \
    -e RUNDECK_DATABASE_DRIVER=org.mariadb.jdbc.Driver \
    -e RUNDECK_DATABASE_USERNAME="${DB_USERNAME}" \
    -e RUNDECK_DATABASE_PASSWORD="${DB_PASSWORD}" \
    -e RUNDECK_DATABASE_URL="${DB_URL}" \
    rundeckpro/enterprise:5.8.0

Example Configurations

The Rundeck Docker Zoo
has many docker compose example projects. Check it out for use as a quick config reference and starting templates!