You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of people will hit registry auth issues. When passing --console=plain, we can see the error and know what went wrong.
$ jib jar --target=openjdk --console=plain ~/tmp/embedded_jetty_hello_world.jar
...
Container entrypoint set to [java, -cp, /app/explodedJar:/app/dependencies/*, org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader]
Container program arguments set to []
[ERROR] I/O error for image [registry-1.docker.io/library/openjdk]:
[ERROR] java.net.SocketException
[ERROR] Socket closed
com.google.cloud.tools.jib.api.RegistryUnauthorizedException: Unauthorized for registry-1.docker.io/library/openjdk
However, by default, it's getting erased by the dynamic progress update. Also the output becomes messy.
$ jib jar --target=openjdk ~/tmp/embedded_jetty_hello_world.jar
...
Container entrypoint set to [java, -cp, /app/explodedJar:/app/dependencies/*, org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader]
Container program arguments set to []
I/O error for image [registry-1.docker.io/library/openjdk]:
java.net.SocketException
Socket closed
I/O error for image [registry-1.docker.io/library/openjdk]:
java.net.SocketException Socket closed
I/O error for image [registry-1.docker.io/library/openjdk]:
java.net.SocketException
Socket closed
I/O error for image [registry-1.docker.io/library/openjdk]:
java.net.SocketException
Socket closed
I/O error for image [registry-1.docker.io/library/openjdk]:
Executing tasks: java.net.SocketException
Socket closed
I/O error for image [registry-1.docker.io/library/openjdk]:
java.net.SocketException
Socket closed
Executing tasks:
[========================== ] 87.2% complete
> pushing blob sha256:421a4fefea8af2cd5590e9952...
> pushing blob sha256:5d3b2c2d21bba59850dac063b...
$
This is a critical issue, as it hides the essential information.
The text was updated successfully, but these errors were encountered:
A lot of people will hit registry auth issues. When passing
--console=plain
, we can see the error and know what went wrong.However, by default, it's getting erased by the dynamic progress update. Also the output becomes messy.
This is a critical issue, as it hides the essential information.
The text was updated successfully, but these errors were encountered: