Open Dudeplayz opened 3 years ago
The same seems to be happening when pulling openjdk:12
so wondering if it's a base image problem.
I also encountered such a problem, is there a solution now?
@taoyoung-it I have specified the maven image more precisely. I'm using atm maven:3.6-adoptopenjdk-11
and maven:3.6-jdk-11
.
Seems to be only a problem with specific versions/images.
rootless >> pasa@astra:~/docutable$ docker pull openjdk:12
12: Pulling from library/openjdk
a316717fc6ee: Extracting 42.61MB/42.61MB
d6d7d7e0184b: Download complete
f63b992b1bff: Download complete
failed to register layer: Error processing tar file(exit status 1): lchown /dev/initctl: no such file or directory
12: Pulling from library/openjdk
a316717fc6ee: Extracting [==================================================>] 42.61MB/42.61MB
d6d7d7e0184b: Download complete
f63b992b1bff: Download complete
failed to register layer: failed to Lchown "/dev/console" for UID 0, GID 0: lchown /dev/console: no such file or directory```
This is probably an issue with your docker, likely using an old version
Description
I am using the
maven:latest
docker build in my ci/cd setup (Gitlab + Gitlab Runner - Self Managed). Starting last Thursday my build fails with the following messageERROR: Preparation failed: failed to register layer: ApplyLayer exit status 1 stdout: stderr: lchown /dev/initctl: no such file or directory (docker.go:143:148s)
.I also tried to manually pull the docker image from the console and getting the same error:
failed to register layer: ApplyLayer exit status 1 stdout: stderr: lchown /dev/initctl: no such file or directory
. I tried to pull another maven image and it worked. I tested it withmaven:maven:3.6-adoptopenjdk-11
. The console looks like this when the error occurs:It is hanging for some seconds on Extracting of
a73adebe9317
(42.07MB/42.07MB) until it crashes.I am not sure if it is related to this image or if it's a general docker problem. I have found this similar issue: https://github.com/moby/moby/issues/41803
Additional informormations
Containerized environment: Proxmox VE with Debian LXC container running docker-ce
docker version
``` Client: Docker Engine - Community Version: 20.10.2 API version: 1.41 Go version: go1.13.15 Git commit: 2291f61 Built: Mon Dec 28 16:17:34 2020 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.2 API version: 1.41 (minimum version 1.12) Go version: go1.13.15 Git commit: 8891c58 Built: Mon Dec 28 16:15:28 2020 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.3 GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b runc: Version: 1.0.0-rc92 GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff 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.5.1-docker) Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 10 Server Version: 20.10.2 Storage Driver: vfs 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.runtime.v1.linux runc io.containerd.runc.v2 Default Runtime: runc Init Binary: docker-init containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff init version: de40ad0 Security Options: seccomp Profile: default Kernel Version: 5.4.78-2-pve Operating System: Debian GNU/Linux 10 (buster) OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 4GiB Name: runner1 ID: I2LW:4YXH:XY7H:A3DE:F47G:JZB2:OI7L:N5GJ:WLYW:X4BT:RGRI:YFC5 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 blkio weight support WARNING: No blkio weight_device support ```