This document discusses how Octopus Deploy can be used to automate deployments of Docker containers. It maps Octopus concepts like feeds, packages, and versions to Docker concepts like registries, images, and tags. It also outlines the requirements to enable Docker support in Octopus and how built-in conventions allow Octopus to automatically deploy Docker images to different environments while also allowing for custom deployment actions using PowerShell scripts.

1. Sensitivity: Internal

2. Octopus Deploy &
Docker
Pedro Sousa @psousa75

3. DevScope
Where I Work
Systems Engineer
What I Do
@psousa75
pedro.sousa@devscope.net
Where To Find Me

5. Build servers are great at:
•
•
•
•
•
•
•
Octopus is great at:

6. Dev
Octopus is a deployment automation server
Ops

7. •
•
•
•
•
•

8. •
•
•
•
•
•
•

10. How Docker containers map to Octopus concepts
In Octopus Deploy, a deployment usually involves a versioned instance of package that is obtained from some
package feed.
With the introduction of support for Docker, a similar concept exists whereby a Docker Registry exposes a list of
Images which can be tagged with one (or more) values.

11. The Octopus concepts of feeds, packages and versions can be mapped
to the Docker concepts of registries, images and tags.

12. • Version 3.5 or higher (current release: )
• Enable Docker Support

15. Built-in conventions mean that Octopus automatically takes care of:
•
•
•
•
•
Custom deployment actions can also be performed using PowerShell. Your environment-specific variables will be
passed to the script, allowing you to perform custom actions depending on the environment…

18. #MSOSCAMP