octopusdeploy/tentacle
Tentacle agent for Octopus Deploy - https://octopus.com
10M+
This image can be used to bring up an Octopus Tentacle in a container.
Docker containers are supported on Windows Server 2016 and Windows 10.
Make sure you've enabled the containers feature:
Enable-WindowsOptionalFeature -Online -FeatureName containers –All
If you want to run with Hyper-V isolation, enable Hyper-V as well:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V –All
You will also need Docker for Windows installed.
On Linux containers, prior to version 6.1.1271
the internal listening port was set by the ListeningPort
environment variable. Any containers which previously exposed Tentacle on a port other than 10933
will need to have their port configuration updated if updating to a version >=6.1.1271
. For example if the container was run with -p 10934:10934
this should be updated to -p 10934:10933
.
On a Windows Server 2016 server, or on Windows 10, run:
docker run --publish 10931:10933 `
--tty --interactive `
--env ListeningPort="10931" `
--env ServerApiKey="API-WZ27UDXXAPCKUPZSH1WTG8YC80G" `
--env TargetEnvironment="Test" `
--env TargetRole="app-server" `
--env ServerUrl="https://octopus.example.com" `
--env PublicHostNameConfiguration="ComputerName" `
--env ACCEPT_EULA="Y" `
octopusdeploy/tentacle
It is recommended that you run this using something like docker compose, so that it sets up and handles networking for you. Please see the docker-compose.yml
file in the Octopus Tentacle repo for an example. Otherwise, use docker network
so that the containers can talk to each other.
ServerUrl
. Implies a polling Tentacle.PublicIp
, FQDN
, ComputerName
or Custom
. Defaults to PublicIp
.PublicHostNameConfiguration
is set to Custom
, the host name that the Octopus Server should use to communicate with the Tentacle.Please contact Octopus Support for support.
docker pull octopusdeploy/tentacle