Resolve Issue When Using a Self-Hosted GitLab Instance for the Container Registry on a Self-Hosted Gitpod Instance #8795
Labels
meta: never-stale
This issue can never become stale
team: delivery
Issue belongs to the self-hosted team
team: workspace
Issue belongs to the Workspace team
Bug description
When attempting to use the container registry of a self-hosted GitLab instance the following error is displayed in the Gitpod UI when bringing up a new workspace:
This message seems a bit misleading if I am to also believe what is shown in the image-builder-mk3 logs:
As you can see it looks like an authorization error. I have tried setting up the
container-registry-token
using my GitLab administrator account to create a personal access token as well as my "normal" user account but both cause the same error message as seen above. When I create the PAT I create it with theapi
,read_registry
andwrite_registry
scopes.Here's some logs from GitLab (
/var/log/gitlab/registry/current
- 0.0.0.0 indicates my home public IP):And from
/var/log/gitlab/nginx/gitlab_registry_access.log
:I also noticed in the messages from the image-builder-mk3 pod -
pull access denied, repository does not exist or may require authorization
so I am wondering if something else needs to be done when using GitLab as a container registry? Does a group, or project also need to be created before hand? For what it's worth, I do have a group called 'workspace-images' to which I have pushed theworkspace-full:latest
image to.I am running my GitLab Container Registry instance under it's own domain (main GitLab is at gitlab.gitpodbread.com, registry is at registry.gitpodbread.com). Related
gitlab.rb
config:Gitpod configuration -
gitpod.config.yaml
:If any more of my setups settings or information can be provided to further troubleshoot this please let me know! cc. @mrsimonemms
Steps to reproduce
Workspace affected
No response
Expected behavior
I would expect that Gitpod be able to utilize the GitLab Container Registry for itself.
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: