Closed
Description
When building containers FROM another container image I've built locally, Docker build is failing to find the image and searching externally. A couple weeks ago, I saw this issue and found the problem was mitigated by disabling build kit (DOCKER_BUILDKIT=0
) However, this no longer works.
Notably, this is a paradigm I've been following for years- I've searched all over dockers documentation and can not find any relevant changes documented.
This is what I'm seeing, The amd64/wtfbbqhax_runtime
is just an alpine image that I have locally.
bash$ cat Dockerfile
FROM amd64/wtfbbqhax_runtime:7b2d02df45e4 as runtime
RUN apk add gdb
COPY cores/ /storage/cores
ENTRYPOINT []
bash$ docker images | grep amd64
amd64/wtfbbqhax_runtime latest 7b2d02df45e4 3 hours ago 89.1MB
bash$ docker build -t wtfbbqhax-debug .
[+] Building 1.8s (3/3) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 196B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> ERROR [internal] load metadata for docker.io/amd64/wtfbbqhax_runtime:7b2d02df45e4 1.6s
------
> [internal] load metadata for docker.io/amd64/wtfbbqhax_runtime:7b2d02df45e4:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied,
repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Metadata
Metadata
Assignees
Labels
No labels