-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No progress after "Container entrypoint set to" with jib-maven-plugin 3.4.3 #4267
Comments
We are facing the same problem when upgrading to jib-maven-plugin 3.4.3. It seems to be a Windows-only problem (it works correctly when running the command in WSL2/Ubuntu) Staying on 3.4.2 for now. |
Breaking change is addition of the following line. jib/jib-core/src/main/java/com/google/cloud/tools/jib/builder/steps/StepsRunner.java Line 624 in ec44330
This line blocks until jib/jib-core/src/main/java/com/google/cloud/tools/jib/docker/CliDockerClient.java Line 192 in ec44330
Can be reproduced on windows with following code. Only occurs with
|
@mpeddada1 this I believe was introduced in 3.4.3 and looks to be an important regression issue to fix before making the next release. |
@chanseokoh Assigned this to myself.
|
We encountered this issue as well. Seems to be working on linux but hanging on windows. Doing a breakpoint on line 191 in CliDockerClient and calling waitFor() hangs on windows. If you call getInputStream() without calling waitFor() before it, it works as expected. Downgraded to 3.4.2 in the meantime. |
jib-maven-plugin 3.4.4 has been released (https://github.com/GoogleContainerTools/jib/releases) to address #4265 and #4265. Please let us know if you're running into any further issues! |
@mpeddada1
Downgraded to 3.4.2 solve the issue. |
@awbit |
+1, It still hanging on Windows when execute |
It doesn't work for us on Windows either. However, it works if we run the command in WSL. |
Re-opening will try to prioritize, in the meantime if anyone in the community has a fix we would welcome a community contribution for this one! |
Environment:
Description of the issue:
After upgrading to jib-maven-plugin 3.4.3 the progress stops after "Container entrypoint set to". With jib-maven-plugin 3.4.2 the build succeeds.
Expected behavior:
The build succeeds.
Steps to reproduce:
jib-maven-plugin
Configuration:Log output:
The output for jib-maven-plugin 3.4.2
Additional Information:
The build is triggered by skaffold with additional parameter
-Djib.to.tags=local
.The text was updated successfully, but these errors were encountered: