Running the Octopus Deploy Server inside a container provides a simple way to set up an Octopus Deploy instance. Upgrading to the latest version of Octopus is just a matter of running a new container with the new image version.
Although there are a few different configuration options, a simple example of starting up an Octopus Deploy server container is as follows:
docker run --interactive --detach ` --name OctopusServer ` --publish "1322:81" ` --env sqlDbConnectionString="Server=172.23.192.1,1433;Initial Catalog=Octopus;Persist Security Info=False;User ID=sa;Password=P@ssw0rd;MultipleActiveResultSets=False;Connection Timeout=30;" ` --volume "E:/Octopus/Logs:C:/TaskLogs" ` octopusdeploy/octopusdeploy:2018.3.13
We run in detached mode with
--detach to allow the container to run in the background.
--interactive argument ensures that
STDIN is kept open which is required since internally this is what the running
Octopus.Server.exe process is waiting on to close.
--name OctopusServer just gives us an easy to remember name for this container. This is optional, but we recommend you provide a name that is meaningful to you, as that will make it easier to perform actions on the container later if necessary.
--publish "1322:81" we are mapping the container port
1322 on the host so that the Octopus instance is accessible outside this sever.
To set the connection string we provide an environment variable
sqlDbConnectionString (in this case, to a local SQL server).
In this example, we are running the image
octopusdeploy/octopusdeploy:2018.3.13. The tag maps directly to the Octopus Server version that is bundled inside the image.
When running an Octopus Server Image, the following values can be provided to configure the running Octopus Server instance.
Read the Docker docs about setting environment variables.
|SqlDbConnectionString||Connection string to the database to use|
|MasterKey||The master key to use to connect to an existing database. If not supplied, and the database does not exist, it will generate a new one. If the database does exist, this is mandatory|
|OctopusAdminUsername||The admin user to create for the Octopus Server|
|OctopusAdminPassword||The password for the admin user for the Octopus Server|
Exposed Container Ports
Read Docker docs about exposing ports.
|81||Port for API and HTTP portal|
|10943||Port for Polling Tentacles to contact the server|
The Octopus Server container does not currently support HTTPS however this should be available sometime in the future
Read the Docker docs about mounting volume.
|C:\Import||Imports from this folder if Octopus Migrator metadata.json exists then migrator
|C:\Repository||Package path for the built-in package repository|
|C:\Artifacts||Path where artifacts are stored|
|C:\TaskLogs||Path where task logs are stored|
When the volumes are externally mounted to the host filesystem, upgrades between Octopus versions are much easier. We can picture the upgrade process with a container as being similar to moving a standard Octopus Server since containers, being immutable, don't themselves get updated.
Similar to moving an instance, to perform the container upgrade you will need the master key that was used to set up the original database. The master key for an Octopus Server in a container can be found by using the container exec command.
> docker container exec <container name/ID> 'C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe' show-master-key --console --instance OctopusServer 5qJcW9E6B99teMmrOzaYNA==
When you have the master key, you can stop the running Octopus Server container instance (delete it if you plan on using the same name), and run almost the same command as before, but this time, passing in the master key as an environment variable and referencing the new Octopus Server version. When this new container starts up, it will use the same credentials and detect that the database has already been set up and use the master key to access its sensitive values.
docker run --interactive --detach ` --name OctopusServer ` --publish "1322:81" ` --env sqlDbConnectionString="Server=172.23.192.1,1433;Initial Catalog=Octopus;Persist Security Info=False;User ID=sa;Password=P@ssw0rd;MultipleActiveResultSets=False;Connection Timeout=30;" ` --volume "E:/Octopus/Logs:C:/TaskLogs" ` --env masterKey=5qJcW9E6B99teMmrOzaYNA== ` octopusdeploy/octopusdeploy:2018.4.0
While you don't strictly need to mount the internal directory locations, it will mean that the newly upgraded server will still have access to all the same packages, logs, and artifacts as before. The standard backup and restore procedures for the data stored on the filesystem and the connected SQL Server still apply as per normal Octopus installations.