Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steps run on Octopus Server cannot use execution container that requires authentication #6900

Closed
6 tasks done
geofflamrock opened this issue May 31, 2021 · 3 comments
Closed
6 tasks done
Assignees
Labels
area/core feature/docker kind/bug This issue represents a verified problem we are committed to solving

Comments

@geofflamrock
Copy link

geofflamrock commented May 31, 2021

Prerequisites

  • I have verified the problem exists in the latest version
  • I have searched open and closed issues to make sure it isn't already reported
  • I have written a descriptive issue title
  • I have linked the original source of this report
  • I have labelled the value stream (area/core, area/steps, ...)
  • I have tagged the issue appropriately (kind/bug, kind/enhancement, feature/ ...)

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

  1. Create a private docker registry (e.g. gitlab)
  2. Create a feed in Octopus for this registry, setting credentials (for gitlab this means using an access token)
  3. Create a deployment process/runbook with a step that uses the default worker pool, and ensure that steps are allowed to run on Octopus Server.

The package acquisition will fail with access denied.

Screen capture

image

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

@geofflamrock geofflamrock added kind/bug This issue represents a verified problem we are committed to solving feature/docker area/core labels May 31, 2021
@octoreleasebot
Copy link

Release Note: Steps run on Octopus Server using execution containers will now authenticate to Docker registries correctly

@Octobob
Copy link
Member

Octobob commented Aug 11, 2021

🎉 The fix for this issue has been released in:

Release stream Release
2020.6 2020.6.5116
2021.1 2021.1.7289
2021.2 2021.2.4545
2021.3+ all releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core feature/docker kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants