Use aproxy for the oci-publish step for self-hosted runners #158
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
plars
force-pushed
the
use-aproxy-oci-publish
branch
from
10a0cc9 to
8c8db04
Compare
omar-selo
approved these changes
Nov 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
self-hosted runners have very restrictive rules for network access. As a result, pulling docker base images to build and publish OCI images requires a proxy. IS devops has been working on this solution called aproxy, which will eventually be installed by default on the self-hosted runners. So eventually we can just remove this section from the workflow, but for now it's needed in order to get OCI image publishing working again.
Testing
I ran the action against this branch and it passed here: https://github.com/canonical/testflinger/actions/runs/6795492316/job/18473690576