Docker build not successful with Buildpacks

Image Builds
1

Hi there,

while building the image with Buildpacks the below error comes,

image
image1906×656 44.8 KB

Kindly let me know, what might be the issue.

Thanks,
Sujit Ray

2

The problem is likely the outdated API version that the builder wants to use.

https://docs.docker.com/reference/api/engine/#deprecated-api-versions

We have quite a few topics about that like this one

I your case, you might want to switch to the Noble variant

https://hub.docker.com/r/paketobuildpacks/builder-noble-java-tiny

Sicne the Ubuntu distribution is newer on which the image was based, maybe it uses a newer client that supports the current minimum Dcoker API version.

If that doesn’t work, you can try searching for Java-related topics about “minimum api version” or someone could share a more related topic than I did. But it is really the responsibility of the client to support the right API version. This is not even a very new change now.

3

Hi @rimelek,

Thanks for your prompt reply,

I want to share my docker version installed in my local. this is latest version installed on my machine

image
image1913×711 21.5 KB

Thanks,
Sujit Ray

4

Yes, the latest version is installed on your machine and the minimum API version in the latest version is 1.40, while your builder tries to use 1.24 according to your screenshot. The screenshot also confirms your minimum api version

By the way, we prefer looking at texts shared as code blocks, because that is searchable and we can copy or quote part of it. Screenshots are often hard to see although yours were okay. Still, please, try not to share screenshots of texts whenever you have a way to copy and share the texts as code blocks formatted in markdown: https://forums.docker.com/t/how-to-format-your-forum-posts/127295#p-202628-dockerfiles-compose-files-logs-and-code-4

Back to your question: I still had this forgotten in my docker daemon’s config:

"min-api-version": "1.24"

That made 1.24 the minimum version, but as I linked before, any version below 1.44 is deprecated the real solutions are fixing the clients not downgrading the servers. You can still do that temporarily, but there is no guarantee that everything will work.

5

Hi @rimelek ,

Many thanks for your input. I changed the spring boot maven plugin version to the updated one 3.5.12, and it worked for me.

Thanks,
Sujit Ray

6

Thank you for your feedback. Please, consider marking whichever post you think was the solution as “solution” by clicking on the checkbox icon under the post. You may need to click on the three dots first if the checkbox is not visible.