[GH-ISSUE #657] Gitlab Registry - Unauthorized #2344

Closed
opened 2026-04-11 10:16:20 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @LeeRoyManea on GitHub (Jul 11, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/657

Does someone know how to get my Private Registry working with Komodo?

I have added a Registry Account with UserName and AccessToken.
The Domain has the following format:

  • "registry.gitlab.mydomain.com"

But i tested a couple of possibilities. With https and without.
When i run the compose file manualy on the same Server everything works.
But not through Komodo.
Has someone an Idea what im doing wrong?

Originally created by @LeeRoyManea on GitHub (Jul 11, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/657 Does someone know how to get my Private Registry working with Komodo? I have added a Registry Account with UserName and AccessToken. The Domain has the following format: - "registry.gitlab.mydomain.com" But i tested a couple of possibilities. With https and without. When i run the compose file manualy on the same Server everything works. But not through Komodo. Has someone an Idea what im doing wrong?
GiteaMirror added the setup label 2026-04-11 10:16:20 -05:00
Author
Owner

@Rauks commented on GitHub (Jul 15, 2025):

Hi,

I'm currently using a private Gitlab self-hosted registry, the stacks using it are defined as below:

[[stack]]
name = "my-stack"
[stack.config]
server = "my-server"
project_name = "my-stack"
linked_repo = "my-stack-repository"
file_paths = ["docker-compose.yml"]
registry_provider = "registry.mydomain.com"
registry_account = "gitlab+deploy-token-my-registry-account"

The registry account is defined in Komodo UI with:

  • The registry domain registry.mydomain.com as domain (without http/https).
  • A Deploy Token created on the top-level group of the Gitlab registry/project.
    • The token user as registry account username and used as registry_account in the stack definition (in the stack example above, gitlab+deploy-token-my-registry-account).
    • The token itself as registry account password.
  • The token having the read_registry scope.
<!-- gh-comment-id:3072563135 --> @Rauks commented on GitHub (Jul 15, 2025): Hi, I'm currently using a private Gitlab self-hosted registry, the stacks using it are defined as below: ```yaml [[stack]] name = "my-stack" [stack.config] server = "my-server" project_name = "my-stack" linked_repo = "my-stack-repository" file_paths = ["docker-compose.yml"] registry_provider = "registry.mydomain.com" registry_account = "gitlab+deploy-token-my-registry-account" ``` The registry account is defined in Komodo UI with: - The registry domain `registry.mydomain.com` as domain (without http/https). - A **Deploy Token** created on the top-level group of the Gitlab registry/project. - The token user as registry account username and used as `registry_account` in the stack definition (in the stack example above, `gitlab+deploy-token-my-registry-account`). - The token itself as registry account password. - The token having the `read_registry` scope.
Author
Owner

@Blacks-Army commented on GitHub (Jan 30, 2026):

@mbecker20 I’m experiencing the same issue. I have three registry accounts: index.docker.io, my private Forgejo registry (with private repos and packages), and dhi.io. The first two work without explicitly defining them, but the third does not.

<!-- gh-comment-id:3824688422 --> @Blacks-Army commented on GitHub (Jan 30, 2026): @mbecker20 I’m experiencing the same issue. I have three registry accounts: index.docker.io, my private Forgejo registry (with private repos and packages), and dhi.io. The first two work without explicitly defining them, but the third does not.
Author
Owner

@ReclaimedBytes commented on GitHub (Mar 22, 2026):

I'm also unable to get dhi.io to work through Komodo.

<!-- gh-comment-id:4106487249 --> @ReclaimedBytes commented on GitHub (Mar 22, 2026): I'm also unable to get dhi.io to work through Komodo.
Author
Owner

@mbecker20 commented on GitHub (Mar 23, 2026):

@ReclaimedBytes you should open a new issue for dhi.io

<!-- gh-comment-id:4107280898 --> @mbecker20 commented on GitHub (Mar 23, 2026): @ReclaimedBytes you should open a new issue for dhi.io
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#2344