Unable to upgrade to 9.9.3-developer docker image on docker 1.13.1 - missing signature key

SonarQube Server / Community Build
, ,
1

- What version are you upgrading from?

9.9.2-developer

- What’s the issue you’re facing?
We are using openshift 3.11 which uses docker 1.13.1. With the latest lts-developer docker image update to 9.9.3-developer, the docker is not able to download the image as it is no longer compatible with it.

Docker image version 9.9.2-developer works fine, version 9.9.3-developer fails with error “missing signature key”.

Did you change the building proces between versions 9.9.2 and 9.9.3? Probably changed docker to podman/buildah? Or upgraded docker? Or removed --format=docker build parameter?

docker pull sonarqube:9.9.2-developer
Trying to pull repository docker.io/library/sonarqube ...
9.9.2-developer: Pulling from docker.io/library/sonarqube
43f89b94cd7d: Pull complete
a4452d37e1e4: Pull complete
cae6cc00f059: Pull complete
dfaec5da5e63: Pull complete
eb7dcc43773c: Pull complete
929496fefe16: Pull complete
2777abd04011: Pull complete
Digest: sha256:f41bd1d2837ebcce281d8342890c9d7dd6de881f2eaeacfae5d1ac189f1674d6
Status: Downloaded newer image for docker.io/sonarqube:9.9.2-developer

docker pull sonarqube:9.9.3-developer
Trying to pull repository docker.io/library/sonarqube ...
missing signature key

- System information (Operating system, Java version, Database provider/version)

Output of docker version command

Client:
Version:         1.13.1
API version:     1.26
Package version: docker-1.13.1-209.git7d71120.el7.centos.x86_64
Go version:      go1.10.3
Git commit:      7d71120/1.13.1
Built:           Wed Mar  2 15:25:43 2022
OS/Arch:         linux/amd64
 
Server:
Version:         1.13.1
API version:     1.26 (minimum version 1.12)
Package version: docker-1.13.1-209.git7d71120.el7.centos.x86_64
Go version:      go1.10.3
Git commit:      7d71120/1.13.1
Built:           Wed Mar  2 15:25:43 2022
OS/Arch:         linux/amd64
Experimental:    false
4

Dear @Michal_Valach,

thanks for posting in our community forum!

We did not change the build process between the two releases. I was actually able to pull sonarqube: 9.9.3-developer without issues. I notice that you run on a very old docker engine, as 1.31.1 was released in 2017. May I ask you to upgrade your docker server version and try again?

As mentioned in the docs, we recommend using Docker Engine version 20.10 and above.

5

Thank You for the quick test and reply.

I know the problem is docker version 1.13.1 as it is old but I am unable to upgrade it to newer version currently.

Since version 9.9.2 is working on version 1.13.1. and version 9.9.3 is not, there must have been some sort of change in building process, probably just simple docker update?

If I am reading it correctly, docker changed default image format in release 25, which was released January 2024. Did You upgrade to docker 25?

6

Hi @Michal_Valach,

Thanks for providing additional info about your current situation.

Since version 9.9.2 is working on version 1.13.1. and version 9.9.3 is not, there must have been some sort of change in building process, probably just simple docker update?

The building process of the official images is directly managed by DockerHub in this repository. The SonarQube image is one of them. We test the Dockerfile in-house and then we submit the Dockerfile to the DockerHub folks. Therefore, the exact docker engine used to build the final image cannot be set by us.

If I am reading it correctly, docker changed default image format in release 25, which was released January 2024. Did You upgrade to docker 25?

The 9.9.3 got released last November (corresponding PR here). However, official images get rebuilt very often to incorporate security patches made available to the base image (eclipse-temurin in our case). I assume that DockerHub builds its images using the latest and most reliable docker engine.