This link https://octopus.com/docs/installation/octopus-in-container/octopus-server-container refers to running octopus in a container. We’re trying this out on an Azure VM and it works ok so far however, obviously we want to ensure we run the site under SSL and our own URL, as we would for Octopus running on a standard VM.
The web link states that SSL is not supported; this sort of means that octopus deploy in a container cannot be used in publically available web hosts such as Azure as the login credentials are sent in plain text.
It’s listed as “coming soon”. When will SSL support be enabled?
Thanks for reaching out.
Unfortunately, the limitation here would be that the docker image doesn’t expose any configuration for passing in certificates to support HTTPS.
The solution might be to place the container behind a load balancer that can be configured with SSL termination like the Application Gateway. Also, take a look at Azure’s documentation on adding HTTPS to an Azure container instance. At the moment there is no release date set for SSL Support on the Octopus side.
I realize this may not be the answer you were looking for but do let me know if you have further questions or concerns.
Ok - One suggestion would be to remove the “coming soon”, as it isn’t true and add a suggestion to run the octopus container behind a reverse proxy (which could itself be a container) such as Application Gateway, IIS/ARR or nginx which can then handle the SSL termination and redirect to the octopus container over HTTP.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.