Replies: 1 comment 1 reply
-
Not sure how gcloud image registry works. But if it helps, all CapRover does is to pass username and pass in the header when it makes an API call to docker engine. Think of this as simple values that your provide to |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi! I'm in the process of setting up CI/CD by using the Caprover docs, and instead of GitLab, I am using GCloud's cloudbuild to deploy private images to their google registry url
gcr.io
. In my captain dashboard, it shows that GCloud can be used as a remote registry. However, I am a bit confused on how to authenticate. Google provides us with the following authentication methods:Reference: https://cloud.google.com/artifact-registry/docs/docker/authentication#standalone-helper
Obviously it would be great to use the access token method like GitLab, however gclouds access tokens are short-lived (60 minutes) so I'm a bit confused on how I set up a remote registry, especially when I do have to scale up using clusters, knowing when to re-auth before a new image needs to be pulled could cause an issue.
What would be the best approach to authenticate with gcloud so that I can pull the remote image using the
--imageName
flag while runningcaprover deploy
?Beta Was this translation helpful? Give feedback.
All reactions