hernanDatgDev commented on issue #5007:
URL: https://github.com/apache/camel-k/issues/5007#issuecomment-1881804664
@gansheer Unfortunately I'm still facing this unauthorized 401 registry
issue with the latest release 2.2.0
This occurs in both my docker-desktop cluster and a local Minikube (with &
without internal registry enabled)
Were you able to reproduce the error?
These are the latest steps I have for v 2.2.0:
1. `kamel install --registry docker.io --organization hguardado
--registry-secret dockerhub-cred \
--build-publish-strategy Jib`
2. `kamel run src/main/groovy/timer-log.groovy --dev`
Log snippet from builder pod init-container: jib
```
{"level":"error","ts":"2024-01-08T20:47:58Z","logger":"camel-k.maven.build","msg":"Failed
to execute goal com.google.cloud.tools:jib-maven-plugin:3.3.2:build
(default-cli) on project camel-k-integration: Build image failed, perhaps you
should make sure your credentials for
'registry-1.docker.io/hguardado/camel-k-kit-cme5uej3kd2c73eeqvqg' are set up
correctly. See
https://github.com/GoogleContainerTools/jib/blob/master/docs/faq.md#what-should-i-do-when-the-registry-responds-with-unauthorized
for help: Unauthorized for
registry-1.docker.io/hguardado/camel-k-kit-cme5uej3kd2c73eeqvqg: 401
Unauthorized
```
Full log:
[builder.log](https://github.com/apache/camel-k/files/13866173/builder.log)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
