Fail to Get Docker Package

I have created a project that runs the “Run a Docker Container” step.

It is using SSH to a Linux server. I had it working, but then I switched it to a tenanted deploy and now I am getting an error that it was not able to download the docker container.

22:38:21   Error    |         NotSpecified: You will need docker installed and running to pull docker images
22:38:21   Error    |         At C:\Octopus\Tentacle\Work\20200905223814-1253-5\Bootstrap.Octopus.DockerPull.ps1:962 char:2
22:38:21   Error    |         +     . '.\Octopus.DockerPull.ps1'
22:38:21   Error    |         +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
22:38:21   Error    |         at <ScriptBlock>, C:\Octopus\Tentacle\Work\20200905223814-1253-5\Octopus.DockerPull.ps1: line 30
22:38:21   Error    |         at <ScriptBlock>, C:\Octopus\Tentacle\Work\20200905223814-1253-5\Bootstrap.Octopus.DockerPull.ps1: line 962
22:38:21   Error    |         at <ScriptBlock>, <No file>: line 1
22:38:21   Error    |         at <ScriptBlock>, <No file>: line 1
22:38:21   Error    |         Failed to download package MYPRIVATE/DOCKERREPO v1087 from feed: ''
22:38:21   Error    |         Unable to pull Docker image
22:38:21   Verbose  |         Process C:\windows\system32\WindowsPowershell\v1.0\PowerShell.exe in C:\Octopus\Tentacle\Work\20200905223814-1253-5 exited with code 1
22:38:21   Verbose  |         Exit code: 1
                    |   == Skipped: Step 1: Run a Docker Container ==
22:38:21   Info     |     Step "Run a Docker Container" runs only when all previous steps succeeded; skipping

I have Docker fully running on the server. It worked before, and the version of my docker repo does exist. Not sure where to go from here with that error?

Hi Brandon,

Thanks for getting in touch! From the snippet you have attached I can see that Octopus is attempting to execute a .ps1 script here. The first thing that comes to mind is that Octopus will automatically execute .ps1 or .sh based on the target being deployed to. So it appears that Octopus is attempting this deployment on a Windows target.

Our current thought here is that a worker was added to the default worker pool disabling the built-in worker. If the worker added to the default pool is a windows target, you could expect to see this sort of issue.

Would you be able to take a look at your worker pool and confirm that the worker in the default pool is not a windows target?

If you have any further questions or thoughts on this, please don’t hesitate to let me know.

Best regards,

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