Building docker image with spring boot 2.4.1 failes with “Missing 'io.buildpacks.stack.id' stack label” when behind a firewall

[kajh]

I'm, trying to build a docker image with ./mvnw -DskipTests spring-boot:build-image using spring boot 2.4.1 and java 11 (openjdk version "11.0.9" 2020-10-20 LTS) on RHEL7.

I do this on a host behind a strict firewall so I have to fetch the build- and runimage from a private repo. I have configured the spring-boot-maven-plugin to use this repo:

<plugin>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-maven-plugin</artifactId>
    <configuration>
        <docker>
            <builderRegistry>
                <username>my-username</username>
                <password>xxx</password>
                <url>https://my-mirror.com</url>
                <email>kaj.hejer@usit.uio.no</email>
            </builderRegistry>
        </docker>


        <image>
            <builder>my-mirror.com/library/docker.io-paketobuildpacks-builder:base</builder>
            <runImage>my-mirror.com/library/docker.io-paketobuildpacks-run:base</runImage>
            <name>my-mirror.com/my-group/my-app:latest</name>
            <verboseLogging>true</verboseLogging>
        </image>
    </configuration>
</plugin>

The build fails with

[INFO]  > Pulling builder image 'my-mirror.com/library/docker.io-paketobuildpacks-builder:base' 100%
[INFO]  > Pulled builder image 'my-mirror.com/library/docker.io-paketobuildpacks-builder@sha256:cf90221a33966e42f8b1960123dea4406c65fc6a410142ded573ed850ccc313b'
[INFO]  > Pulling run image 'my-mirror.com/library/docker.io-paketobuildpacks-run:base' 100%
[INFO]  > Pulled run image 'my-mirror.com/library/docker.io-paketobuildpacks-run@sha256:56fb7587103da155db6d4f9434fd7e2f9e45d7540a062847fd84e9132a28101b'
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  6.090 s
[INFO] Finished at: 2020-12-17T08:36:48+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:2.4.1:build-image (default-cli) on project my-app: Execution default-cli of goal org.springframework.boot:spring-boot-maven-plugin:2.4.1:build-image failed: Missing 'io.buildpacks.stack.id' stack label -> [Help 1]
[ERROR] 

sudo journalctl -f don't list anything when running the mvnw command.

When I try to build a docker image the same way but without the configuration block for the spring-boot-maven-plugin on my mac which is not behind a firewall it works just fine.

I have asked a question about this on https://stackoverflow.com/questions/65336624/building-docker-image-with-spring-boot-2-4-1-failes-with-missing-io-buildpacks and found a similar question for using gradle on https://stackoverflow.com/questions/65344886/unable-to-build-image-using-gradle-bootbuildimage-in-offline-environment.

[wilkinsona]

It looks like the image in your private repository has lost its io.buildpacks.stack.id label. You can check for its presence using docker inspect. Can you please double-check that the images in your private repository have the same metadata as those available publicly?

[scottfrederick]

When copying the Paketo builder into a private repository, make sure you are copying docker.io/paketobuildpacks/builder not docker.io/paketobuildpacks/build. I've made that mistake before with similar results.

[kajh]

@wilkinsona Thanks for replying! It seems like the "io.buildpacks.stack.id" is present:

$ docker inspect myrepo.com/library/docker.io-paketobuildpacks-builder:base | grep io.buildpacks.stack.id
                "io.buildpacks.stack.id": "io.buildpacks.stacks.bionic",

I diffed docker inspect for the image in my private repo with the one in dockerhub. There are som differences but I'm unsure if they are relevant. I put a textfile with the diff on https://www.dropbox.com/s/ri46btqyn25ws8j/diff.txt?dl=0.

[kajh]

@scottfrederick Thanks for replying! It is the builder image that is copied into our privare repo as far as I can understand. We have a list of images that are synced from dockerhub.

[wilkinsona]

Thanks, @kajh. It could also be the run image that is missing its stack id. Can you please double-check its metadata as well? If that appears to be correct, the stack trace of the failure (available when running Maven with -X) may help.

[kajh]

@wilkinsona Thanks! I have diffed the run-images and the diff is available at https://www.dropbox.com/s/fwv65ovpho0mfup/diff-run.txt?dl=0. Neither of images contains any labels. This is from my mac outside our firewall:

$ docker pull docker.io/paketobuildpacks/run:base 
base: Pulling from paketobuildpacks/run
Digest: sha256:15d03f2ceb34ddedf8be3654d2e1e8ff2f60aa43e1b4f60d0d6b3624b34162dc
Status: Image is up to date for paketobuildpacks/run:base
docker.io/paketobuildpacks/run:base

$ docker inspect  docker.io/paketobuildpacks/run:base | grep Label
            "Labels": null
            "Labels": null

I ran a ./mvnw -X spring-boot:build-image and the buildlog is available at https://www.dropbox.com/s/iwwglb0vv8a6djq/build-image.txt?dl=0

[wilkinsona]

I think that's the wrong run image. The run image is identified in the io.buildpacks.builder.metadata label of the builder. The metadata for docker.io/paketobuildpacks/builder:base lists its run image as index.docker.io/paketobuildpacks/run:base-cnb. Note that's it's base-cnb rather than base.

$ docker inspect index.docker.io/paketobuildpacks/run:base-cnb | grep -C 1 Labels
            "OnBuild": null,
            "Labels": {
                "io.buildpacks.stack.id": "io.buildpacks.stacks.bionic",
--
--
            "OnBuild": null,
            "Labels": {
                "io.buildpacks.stack.id": "io.buildpacks.stacks.bionic",