Steps run on Octopus Server cannot use execution container that requires authentication #6900
Closed
6 tasks done
Labels
area/core
feature/docker
kind/bug
This issue represents a verified problem we are committed to solving
Prerequisites
The bug
When running a step on Octopus Server that uses an execution container docker image from an authenticated docker registry feed, the pull of the docker image to run the step in fails as the credentials aren't being passed to the package acquisition.
What I expected to happen
Steps that run on Octopus Server that use execution container images from authenticated feeds should run correctly.
Steps to reproduce
The package acquisition will fail with access denied.
Screen capture
Affected versions
Octopus Server: 2020.6+
Workarounds
Run the step on a worker other the built-in Octopus Server worker. This can either be achieved by choosing a different worker pool, or disabling running on Octopus Server in Features and adding a specific worker to the default worker pool.
Links
Customer report: https://octopus.zendesk.com/agent/tickets/68199
The text was updated successfully, but these errors were encountered: