spring-boot-version: 2.3.4.RELEASE build system: gradle docker image generated with bootBuildImage
I could not find a place to raise this issue in build pack related sites. It would be nice, If you could forward this information Our spring-boot builds stopped working recently when pushing the docker images generated using bootBuildImage
Pulling builder image 'gcr.io/paketo-buildpacks/builder:base-platform-api-0.3' .................................................. Pulled builder image 'gcr.io/paketo-buildpacks/builder@sha256:9c833b4a053f441248cd90b69ae1172043fbeeba3e35265cb10a88769757aa35' Pulling run image 'docker.io/paketobuildpacks/run:base-cnb' .................................................. Pulled run image 'paketobuildpacks/run@sha256:155ee4b4389fa88b8b9bd5444601417218b3da44e491b1aad8c8b6c2365e7909' Executing lifecycle version v0.9.3 Using build cache volume 'pack-cache-5d730e02ba7.build'
Running creator [creator] ===> DETECTING [creator] 6 of 18 buildpacks participating [creator] paketo-buildpacks/ca-certificates 1.0.1 [creator] paketo-buildpacks/bellsoft-liberica 5.2.0 [creator] paketo-buildpacks/executable-jar 3.1.3 [creator] paketo-buildpacks/apache-tomcat 2.4.1 [creator] paketo-buildpacks/dist-zip 2.2.2 [creator] paketo-buildpacks/spring-boot 3.4.0 [creator] ===> ANALYZING [creator] Previous image with name "OUR-IMAGE-NAME" not found [creator] ===> RESTORING [creator] ===> BUILDING
> Could not push image: manifest invalid: manifest invalid
We noticed that the last working builds where using builder:base-platform-api-0.3 resolving to paketo-buildpacks/bellsoft-liberica 4.0.0
For people having the same issue you can bypass it by executing
./gradlew bootBuildImage --builder=gcr.io/paketo-buildpacks/builder@sha256:00a9c25f8f994c1a044fa772f7e9314fe5d90d329b40f51426e1dafadbfa5ac8
Pulling builder image 'gcr.io/paketo-buildpacks/builder:base-platform-api-0.3' .................................................. Pulled builder image 'gcr.io/paketo-buildpacks/builder@sha256:00a9c25f8f994c1a044fa772f7e9314fe5d90d329b40f51426e1dafadbfa5ac8' Pulling run image 'docker.io/paketobuildpacks/run:base-cnb' .................................................. Pulled run image 'paketobuildpacks/run@sha256:21c1fb65033ae5a765a1fb44bfefdea37024ceac86ac6098202b891d27b8671f' Executing lifecycle version v0.9.2 Using build cache volume 'pack-cache-7072d61fa02b.build'
Running creator [creator] ===> DETECTING [creator] 5 of 17 buildpacks participating [creator] paketo-buildpacks/bellsoft-liberica 4.0.0 [creator] paketo-buildpacks/executable-jar 3.1.1 [creator] paketo-buildpacks/apache-tomcat 2.3.0 [creator] paketo-buildpacks/dist-zip 2.2.0 [creator] paketo-buildpacks/spring-boot 3.2.1 [creator] ===> ANALYZING [creator] Previous image with name "luna-artifactory.ludia.build:6555/api-gateway:0.3.20" not found [creator] ===> RESTORING [creator] ===> BUILDING
:release.master:pushDockerImage (Thread[Execution worker for ':lrelease.master:.release.master',5,main]) completed. Took 15.804 secs.
Comment From: scottfrederick
Could not push image: manifest invalid: manifest invalid
There could be several possible causes for this error, including Artifactory permissions, issues with some versions of the Docker daemon, or a problem with the generated image. If you feel this is a problem with the Paketo builder, the best way to get in touch with that team is via their Slack community.
If you have any further questions, please follow up on Stack Overflow or Gitter. As mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements.