You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation does not mention anything about my problem
There are no open or closed issues that are related to my problem
Description
The docker-containerdriver is needed for caching a base image, however it does not support references to local images, requiring falling back to the docker driver, which does not support caching.
Expected behaviour
As long as an image tag is loaded in a prior action step, a subsequent action step should succeed at referencing that image. (This is the actual behavior when using the dockerdriver.)
Actual behaviour
This works fine when using the docker driver, but using the docker-container default driver, as described in this stackoverflow post, even if you build an image locally prior to building a dependent image, the FROM local/base-builder line will lead to this error:
#2 [internal] load metadata for docker.io/local/base-builder:latest
#2 ERROR: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
#3 CANCELED
This occurs regardless of the format of the image name. This occurs despite verifying that the image was successfully built in a prior step and was successfully loaded.
Repository URL
No response
Workflow run URL
No response
YAML workflow
The below version works, but if I remove driver: docker the second image will fail to build despite the first image being visible in the the output of docker images.
Contributing guidelines
I've found a bug, and:
Description
The
docker-container
driver is needed for caching a base image, however it does not support references to local images, requiring falling back to thedocker
driver, which does not support caching.Expected behaviour
As long as an image tag is loaded in a prior action step, a subsequent action step should succeed at referencing that image. (This is the actual behavior when using the
docker
driver.)Actual behaviour
This works fine when using the
docker
driver, but using thedocker-container
default driver, as described in this stackoverflow post, even if you build an image locally prior to building a dependent image, theFROM local/base-builder
line will lead to this error:This occurs regardless of the format of the image name. This occurs despite verifying that the image was successfully built in a prior step and was successfully loaded.
Repository URL
No response
Workflow run URL
No response
YAML workflow
The below version works, but if I remove
driver: docker
the second image will fail to build despite the first image being visible in the the output ofdocker images
.Workflow logs
No response
BuildKit logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: