Docker 2020.3.6-1809 missing?

Octopus Server
, ,
1

Hi,

I noted that since version 2020.3.5, the OS version is missing in the docker image tag. It is on purpose?

Version 2020.3.4, OS 1809 tag is available

octopusdeploy/octopusdeploy:2020.3.4-1809
https://hub.docker.com/r/octopusdeploy/octopusdeploy/tags?page=1&name=2020.3.4

Version 2020.3.6, OS 1809 tag is missing

octopusdeploy/octopusdeploy:2020.3.6
https://hub.docker.com/r/octopusdeploy/octopusdeploy/tags?page=1&name=2020.3.6

Thanks in advance.

Francis Grignon

3

Hi Francis,

Thanks for getting in touch! The change between the image tags across these versions that you’re seeing is in fact on purpose. We’ve just recently cleaned our process up so that we now only push the manifest itself, where previously it also involved pushing the intermediate tags to Docker Hub.

You shouldn’t need to choose an OS directly. If the image exists, and you do a docker pull octopusdeploy/octopusdeploy:2020.3.6 on a Windows 1809 machine then you’ll get the correct image.

Does that work in your case, or do you rely on the intermediate tags in some way? If you do, we might need to consider adding them back in depending on the use case.

I hope this helps, and I look forward to hearing back!

Best regards,

Kenny

4

Hi @Kenneth_Bates,

We are running Octopus under K8S for more than a year now. It works very well and we are really about it.

I was extending your Docker image to add kubectl since it was not included in your image and it’s required to deploy to k8s.

I build a nice script that was pulling the latest version of octopus for your website, and the build a new image using the version and the OS that we use.

FROM octopusdeploy/octopusdeploy:2019.13.1-1803

But since the OS version is not available, my script doesn’t work anymore since I can’t force a OS. So, I have to use the sha256.

FROM octopusdeploy/octopusdeploy:2020.4.6@sha256:8ec744e1d5483814e9a561907d677c1a7b678c535fb450440d7146575ec74440

I didn’t found a way to find the sha256 automatically. Anyway, I can continue updating it manually.

Francis

5

Hi Francis,

Thanks for following up! That’s awesome to hear this has been working well for you so far, and also that you’ve been able to get around this change for now. Thanks for the elaboration, and it’s something certainly worth bringing up with my team for consideration.

If you have any questions in the meantime, please don’t hesitate to reach out!

Best regards,

Kenny

6

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.