Building images fails with Docker 25.0 when custom buildpacks are configured #39323
Comments
spring-projects-issues
added
the
status: waiting-for-triage
|
I'm experiencing the same issue with bootBuildImage after updating to Docker 25.01:
|
|
The Maven |
scottfrederick
added
type: bug
scottfrederick
changed the title
|
@scottfrederick We are faced the same issue on Spring Boot 2.7.12. Stacktrace seems very similar |
|
@maksimkurb it is not relative to the springboot version but to the plugin itself. That's why the error can be observed on all environment according to thei buildpack selection |
|
@maksimkurb Spring Boot 2.7.x is out of open source support. Please upgrade to a supported version as we won't release any new maintenance version for this generation. |
|
@maksimkurb It is strange that this doesn't fail every time for you. I would be interested to know if you can figure out a pattern there. This problem only happens when custom buildpacks are configured in a build file. One work-around would be to create a custom builder that includes all the buildpacks that you need so that listing buildpacks in your build file is not necessary. A custom builder is not a trivial thing to maintain but might be helpful depending on your circumstances. |
scottfrederick
changed the title
|
If it helps, you can substitute in the |
|
Hi, thank you all for answering! I failed to find any pattern, but we are using Gitlab Runners and maybe some of them wasn't upgraded and build succeeded when old runner was used for the pipeline job, but it is only assumption. We temporarily solved issue for us by downgrading Docker; I hope we fully upgrade the rest of our services to SB3.x soon. |
|
I'm using Spring Boot 3.2.2 and I have the same issue. Should I wait for 3.2.3? |
|
Waiting for 22th of February then 😸 |
|
@scottfrederick - with this fix be backwards-compatible to Spring Boot Maven Plugin 2.x? Or, if not, can we use SB Maven Plugin 3.x with a SB 2.x app? |
All Spring Boot 2.x versions are out of OSS support, so new releases of those plugins will not be made publicly available.
This is not something that we make any attempt to support, and is unlikely to work consistenlty. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
dmurat
added a commit
to croz-ltd/klokwrk-project
that referenced
this issue
May 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In SB3.2, I had issues with adding a buildpack (newrelic). (see #39286 )
I fixed it by
This made this
Everything worked well until my laptop upgraded to docker 25.
When running the build with docker
24everything wirks as expected.However, in docker 25 I get the following result
Here is the failing project
the result of
docker infoAlso the same issue can be observed in SB 3.1.5 with following configuration
gives the following issue
I raised an issue on moby project, yet they justly pointed that image can be built with
packutilitypack build -B paketobuildpacks/builder-jammy-base --run-image paketobuildpacks/run-jammy-base:latest -b paketo-buildpacks/ca-certificates@3.6.7 -b paketo-buildpacks/bellsoft-liberica@10.4.4 -b paketo-buildpacks/syft@1.42.0 -b paketo-buildpacks/gradle@7.7.1 -b paketo-buildpacks/executable-jar@6.8.3 -b paketo-buildpacks/dist-zip@5.6.8 -b paketo-buildpacks/spring-boot@5.27.8 -b paketo-buildpacks/new-relic@8.7.0 --volume $(pwd)/src/main/buildpack/new-relic:/platform/bindings/new-relic test-imgafter looking at the code, I see that image is built using docker api. I don't see any specific treatment wth the
tomlfile.Other strange thing:
ca-certificatesto3.6.4, I get the errorfailed to initialize detector: open /cnb/buildpacks/paketo-buildpacks_ca-certificates/3.6.4/buildpack.toml: no such file or directory.With version
3.6.5, it disapears. I did not see anything between version3.6.4and3.6.5The text was updated successfully, but these errors were encountered: