Replies: 1 comment
-
I was able to circumvent this by pushing platform specific tags up instead of doing a push-by-digest. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Overview
I am trying to accomplish the following workflow:
Here are a few restrictions:
So circumvent these, I export the base image to a tar file, as outlined in 'Share image between jobs'. Since I am following the steps in 'Multi-platform image: Distribute build across multiple runners', I need to use the buildx backend to push by digest. Since I am using the buildx backend, I cannot simply load the base tarball into docker, and need to follow the steps in 'Named contexts: Using with a container builder' so that the local image is accessible to buildkit.
Problem
My base image takes about 5 minutes to build:
It takes an additional 3 minutes to load the image into the local registry using
docker push ...
.This is unacceptably slow, this should be 1 minute or less.
Full workflow
Workflow inputs
build-base-images
build-images
My question is:
tag-base-images
step and share the base image between jobs by pushing up to dockerhub and pulling back down, and only using this workflow when we have push permission to dockerhub.Similar links:
Beta Was this translation helpful? Give feedback.
All reactions