Skip to main content
Version: Early Access

Use the Release Docker Images

This topic describes how the Docker image for Digital.ai Release maintains the same behavior as the existing installation ZIP file, ensuring that setup, upgrade, and operational procedures remain consistent.

The /opt/xebialabs/xl-release-server directory contains an extracted installation setup, augmented with directories that are described in Docker Images for Release.

To download a Docker image for Digital.ai Release, see DockerHub - Release Images.

Set Up and Start the Docker Containers​

There are multiple methods to set up and start the Docker image for Release.

For information about running the Release image using Docker Compose, see Running the Docker Containers with Docker Compose.

Start Containers with Quick Run Commands​

important

This setup method does not include persistence and must not be used in production environments.

note

When no volumes are defined, the container maintains the state between stopping and starting.

Run the Release container with the following command:

docker run -d \
  -e ADMIN_PASSWORD=admin \
  -e ACCEPT_EULA=Y \
  -p 5516:5516 \
  --name xl-release xebialabs/xl-release:26.1.0

Digital.ai Release runs on http://localhost:5516. You can sign in with the username admin and password admin.

You must provide a valid license before you can sign in. Go to the URL and enter your license. If you don't have a license, apply for a Digital.ai Release Trial License.

Secure Container Setup Using a Generated Password​

You can make the setup more secure by starting with a generated admin password instead of the default password. We don't recommend including the Digital.ai Release container in an automated test or use case that depends on a known admin password.

If the ADMIN_PASSWORD environment variable is not set and you're starting up for the first time, the container generates a random password and prints it in the logs.

To trigger this behavior, remove the ADMIN_PASSWORD parameter from the Docker run command:

docker run -d -p 5516:5516 -e ACCEPT_EULA=Y --name xl-release xebialabs/xl-release:26.1.0

The generated password is printed when the container starts and can be found at the top of the log file. To view the logs, run the following command:

docker logs xl-release

Search for the following line:

... Generating admin password: [PASSWORD IS PRINTED HERE]

Stop and Remove Containers​

To stop the container, run the following command:

docker stop xl-release

The state of the application is saved in the container. To start it again, run the following command:

docker start xl-release

To remove the container completely, run the following command:

docker rm xl-release
note

Removing the container results in a blank slate. When you run the container again with the simple run command, the database is empty, you receive a new admin password, and you must enter the license again.

Set Up Release for Production Using Persistent Volumes​

note

In production setups, you must define volumes and configure Release to store its state in an external database.

The previous two setups don't persist the configuration, repository, and archive data across container runs. To ensure persistence when reconfiguring, mount volumes at the conf, repository, archive, and reports mount points:

docker run -d \
  -e ADMIN_PASSWORD=admin \
  -e ACCEPT_EULA=Y \
  -p 5516:5516 \
  -v ${HOME}/xl-release-server/conf:/opt/xebialabs/xl-release-server/conf:rw \
  -v ${HOME}/xl-release-server/repository:/opt/xebialabs/xl-release-server/repository:rw \
  -v ${HOME}/xl-release-server/archive:/opt/xebialabs/xl-release-server/archive:rw \
  -v ${HOME}/xl-release-server/reports:/opt/xebialabs/xl-release-server/reports:rw \
  --name xl-release xebialabs/xl-release:26.1.0