I have a Dockerfile which references another image, which is stored locally (overrideable with a build arg):
ARG PARENT=ds_test_base:test
FROM ${PARENT}
The image is there:
$ docker image ls ds_test_base:test
REPOSITORY TAG IMAGE ID CREATED SIZE
ds_test_base test eb69be11f1e5 3 hours ago 10.4GB
When I try to build this Dockerfile with --builder xyz, which is backed by a docker-container driver, I get this:
#3 [internal] load metadata for docker.io/library/ds_test_base:test
#3 ERROR: pull access denied, repository does not exist or may require authorization: authorization status: 401: authorization failed
------
> [internal] load metadata for docker.io/library/ds_test_base:test:
------
Dockerfile:2
--------------------
1 | ARG PARENT=ds_test_base:test
2 | >>> FROM ${PARENT}
3 |
4 | MAINTAINER "Openmail"
--------------------
error: failed to solve: ds_test_base:test: pull access denied, repository does not exist or may require authorization: authorization status: 401: authorization failed
If I try to build it with exactly the same parameters, but omitting --builder xyz, it builds just fine.
$ docker version
Client: Docker Engine - Community
Version: 20.10.8
API version: 1.41
Go version: go1.16.6
Git commit: 3967b7d
Built: Fri Jul 30 19:54:27 2021
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.8
API version: 1.41 (minimum version 1.12)
Go version: go1.16.6
Git commit: 75249d8
Built: Fri Jul 30 19:52:33 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.9
GitCommit: e25210fe30a0a703442421b0f60afac609f950a3
runc:
Version: 1.0.1
GitCommit: v1.0.1-0-g4144b63
docker-init:
Version: 0.19.0
GitCommit: de40ad0
$ docker info
Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.6.1-docker)
scan: Docker Scan (Docker Inc., v0.8.0)
Server:
Containers: 2
Running: 2
Paused: 0
Stopped: 0
Images: 27
Server Version: 20.10.8
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: e25210fe30a0a703442421b0f60afac609f950a3
runc version: v1.0.1-0-g4144b63
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 5.4.0-81-generic
Operating System: Ubuntu 20.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 30.58GiB
Name: ip-10-150-29-76
ID: ZJFE:DJF7:DUGP:WOGK:A66E:IVQS:X6HB:CKP4:SBRG:VROU:ZIBO:GWXF
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
$ docker image ls moby/buildkit
REPOSITORY TAG IMAGE ID CREATED SIZE
moby/buildkit buildx-stable-1 2b537a02e2d9 6 weeks ago 144MB
I have a Dockerfile which references another image, which is stored locally (overrideable with a build arg):
The image is there:
When I try to build this Dockerfile with
--builder xyz, which is backed by a docker-container driver, I get this:If I try to build it with exactly the same parameters, but omitting
--builder xyz, it builds just fine.