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
We noticed that our maven builds were failing recently due to issues when using the official maven image based on openjdk 11.
However, after some investigation with the developers of the maven image, it was noted that at least the openjdk 11 images seem have a corrupted file system when run with a docker engine on CentOS 7.
The permissions of the file system inside the docker image run:
$ sudo docker version
Client: Docker Engine - Community
Version: 19.03.7
API version: 1.40
Go version: go1.12.17
Git commit: 7141c199a2
Built: Wed Mar 4 01:24:10 2020
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.7
API version: 1.40 (minimum version 1.12)
Go version: go1.12.17
Git commit: 7141c199a2
Built: Wed Mar 4 01:22:45 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
Our builds started failing yesterday after the update of the maven image has happened based on the update of openjdk two days ago. The issues can not be reproduced using the version openjdk:11.0.11-jdk-slim
The text was updated successfully, but these errors were encountered:
This is likely due to the update to Debian Bullseye -- you'll need to update Docker, runc, and likely libseccomp on your host.
Alternatively, you can pin to the Buster variants explicitly, but you'll want to deal with this properly sooner or later because the Buster variants won't be maintained forever (openjdk:11-jdk-slim-buster).
We noticed that our maven builds were failing recently due to issues when using the official maven image based on openjdk 11.
However, after some investigation with the developers of the maven image, it was noted that at least the openjdk 11 images seem have a corrupted file system when run with a docker engine on CentOS 7.
The permissions of the file system inside the docker image run:
OS Information:
Docker information:
Our builds started failing yesterday after the update of the maven image has happened based on the update of openjdk two days ago. The issues can not be reproduced using the version
openjdk:11.0.11-jdk-slim
The text was updated successfully, but these errors were encountered: