build-image failures after docker desktop update with 'Illegal char <:> at index 5: npipe:////' #41199
Comments
spring-projects-issues
added
the
status: waiting-for-triage
|
Thanks for the report. Can you please share the complete stack trace? If it's not logged by default, I think it should be if you run Maven with |
wilkinsona
added
the
status: waiting-for-feedback
|
But of course. Stack trace from running with |
spring-projects-issues
added
status: feedback-provided
|
Thanks. I'm trying to determine what's changed in Docker Desktop 4.31. There's mention of |
wilkinsona
added
status: waiting-for-feedback
|
|
spring-projects-issues
added
status: feedback-provided
|
Thanks again. Both contexts look fine in that they both have I suspect that your environment's changed when you upgraded to Docker Desktop 4.31 such that I think you should be able to work around the problem by configuring the host explicitly. Something like this (untested as I don't have easy access to a Windows box): <plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<docker>
<host>//./pipe/dockerDesktopLinuxEngine</host>
</docker>
</configuration>
</plugin> |
wilkinsona
added
status: waiting-for-feedback
|
Same here: After upgrading Docker to 4.31.1 (from 4.30.x), "build-image" fails. The above mentioned workaround works for me (with gradle): |
spring-projects-issues
added
status: feedback-provided
wilkinsona
added
status: waiting-for-feedback
philwebb
added
type: bug
|
Worked with Maven |
wilkinsona
added
the
status: waiting-for-feedback
|
Thanks a lot! |
spring-projects-issues
added
status: feedback-provided
|
I've replicated this locally. I think the issue is that {
"Name": "desktop-linux",
...
"Endpoints": {
"docker": {
"Host": "npipe:////./pipe/dockerDesktopLinuxEngine",
"SkipTLSVerify": false
}
}
} |
philwebb
changed the title
philwebb
changed the title
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
One more occurrence and one more time the workaround fixed the issue. I've have no Docker environmental variables setup in my system. On Windows Ad Machine™, latest update. |
|
@codetheorist If you have the chance, can you try the latest SNAPSHOT to see if the work-around is no longer needed. |
|
so how do i fix this problem. my maven version is 3.31 docker desktop is 4.31.1 . I encounter this problem too. |
|
@sawamura722 there's a workaround for Maven that should work with Docker Desktop 4.31. |
|
Hey guys, I also have this issue. The workaround configuration solves it, thanks! |
|
@wilkinsona thank you for the workaround it worked with the maven. I am at Docker Desktop v4.32 it is reproducible at this version too. So should we expect a fix from team at Docker Desktop ? |
|
No, I don't expect one. The next versions of Spring Boot (3.2.8 and 3.3.2) will cope with the breaking change in Docker Desktop. Until then, please continue to use the workaround. |
|
You can work around this in Docker by going to Builds/"Builder settings" and clicking the ... menu on the "default" builder and choosing use. Unfortunately it resets back to the "desktop-linux" builder each time you restart docker. docker context output for the two builders: |
that's why this is so annoying. The workaround works for me as well, but it has to be re-applied at each restart. If I got it right, docker desktop won't be fixing this, a new spring-boot/mvn compiler will be needed. |
|
A fix has already been made in Spring Boot (hence this issue being closed as completed). It will be released next week. |
It was work for me. |
I can confirm that in our case updating to spring-boot 3.3.2 solved the issue with no other workaround. Thanks everyone |
Lifesaver thanks!!! |
|
In my case resetting docker desktop to factory settings worked for me as I use MacBook pro m3 |
Description
After Docker Desktop upgrade from 4.30.0 to 4.31.1
spring-boot:build-imagestarted failing with:Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:3.2.5:build-image (default-cli) on project siva-webapp: Execution default-cli of goal org.springframework.boot:spring-boot-maven-plugin:3.2.5:build-image failed: Illegal char <:> at index 5: npipe:////./pipe/dockerDesktopLinuxEngineVersions
OS: Windows 11
Java: 17
Docker desktop (for windows):
✅ 4.30.0
❌ 4.31.0
❌ 4.31.1
Spring Boot (with Docker Desktop 4.31.1):
❌ 3.2.5
❌ 3.3.0
❌ 3.3.1
Reproduction
Sample app: DD4J-test-application
Command:
./mvnw spring-boot:build-image -DskipTestsThe text was updated successfully, but these errors were encountered: