Octopus container Tentacle configuration script can't script register tentacle

[adamoctoclose]

Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.

Prerequisites

• [x] I have verified the problem exists in the latest version
• [x] I have searched open and closed issues to make sure it isn't already reported
• [x] I have written a descriptive issue title
• [x] I have linked the original source of this report
• [x] I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

Script to configure tentacle in Octopus the tentacle container always assumes it will register with the Octopus server. If the tentacle can't communicate with the Octopus Server outbound then the tentacle container will fail to start. If you have a tentacle running in listening mode but dosn't have outbound access to the Octopus Server then you can't use the default Octopus Container.

What I expected to happen

There should be an option to include a server thumbprint when starting the container and the option to skip the registerTentacle function.

Affected versions

Octopus Server: 2020.6

Workarounds

Customer can build a custom image for the container and adjust the tentacle configuration script.

[matt-richardson]

This is possible, though it's not very obvious. If you set the ServerPort variable it will go into polling mode and register with the server

(I found this recently on my home setup)