[1.17.0-rc1] Portainer can't connect to Gitea Container registry #9123

New Issue

GiteaMirror · 2025-11-02T08:30:04-06:00

GiteaMirror commented

2025-11-02 08:30:04 -06:00

Originally created by @helmut72 on GitHub (Jun 23, 2022).

Description

Portainer shows following message when adding a Gitea Container registry:

Portainer was not able to use this registry management features. You might need to update the configuration used by Portainer to access this registry.

Note: Portainer registry management features are only supported with registries exposing the [v2 registry API](https://docs.docker.com/registry/spec/api/).

Gitea Version

1.17-rc1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Gitea from Docker

Database

No response

Originally created by @helmut72 on GitHub (Jun 23, 2022). ### Description Portainer shows following message when adding a Gitea Container registry: ``` Portainer was not able to use this registry management features. You might need to update the configuration used by Portainer to access this registry. Note: Portainer registry management features are only supported with registries exposing the [v2 registry API](https://docs.docker.com/registry/spec/api/). ``` ### Gitea Version 1.17-rc1 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Gitea from Docker ### Database _No response_

GiteaMirror added the topic/packages type/feature type/proposal labels 2025-11-02 08:30:04 -06:00

GiteaMirror closed this issue

2025-11-02 08:30:04 -06:00

GiteaMirror commented

2025-11-02 08:30:05 -06:00

@lunny commented on GitHub (Jun 24, 2022):

What's the registry url?

@lunny commented on GitHub (Jun 24, 2022): What's the registry url?

GiteaMirror commented

2025-11-02 08:30:05 -06:00

@helmut72 commented on GitHub (Jun 24, 2022):

Using the same url like on my own Docker registry registry.example.com and in your docs: gitea.example.com.

Both with authentication. Then I wanted to select browse in Portainer and the message appears on gitea.example.com.

Edit: Could it be that browsing in the registry isn't possible?

@helmut72 commented on GitHub (Jun 24, 2022): Using the same url like on my own Docker registry `registry.example.com` and in your docs: `gitea.example.com`. Both with authentication. Then I wanted to select browse in Portainer and the message appears on `gitea.example.com`. Edit: Could it be that browsing in the registry isn't possible?

GiteaMirror commented

2025-11-02 08:30:05 -06:00

@KN4CK3R commented on GitHub (Jun 24, 2022):

/v2/_catalog is not implemented if that endpoint is needed. Is there a way to test your bug with Portainer CE or only with the business version?

@KN4CK3R commented on GitHub (Jun 24, 2022): `/v2/_catalog` is not implemented if that endpoint is needed. Is there a way to test your bug with Portainer CE or only with the business version?

GiteaMirror commented

2025-11-02 08:30:05 -06:00

@helmut72 commented on GitHub (Jun 24, 2022):

Browsing is only supported with business version. Using that because it's free for 5 nodes and it comes with good a good registry browser. I'm limited on time for debugging, will try to do it next days.

@helmut72 commented on GitHub (Jun 24, 2022): Browsing is only supported with business version. Using that because it's free for 5 nodes and it comes with good a good registry browser. I'm limited on time for debugging, will try to do it next days.

GiteaMirror commented

2025-11-02 08:30:06 -06:00

@helmut72 commented on GitHub (Jun 26, 2022):

Back to an SSH for an hour. I've enabled access log in Gitea, but just got this log entry when I want to start browsing with Portainer when the error appears:

"OPTIONS /v2/ HTTP/1.1" 405 0

@helmut72 commented on GitHub (Jun 26, 2022): Back to an SSH for an hour. I've enabled access log in Gitea, but just got this log entry when I want to start browsing with Portainer when the error appears: ``` "OPTIONS /v2/ HTTP/1.1" 405 0 ```

GiteaMirror commented

2025-11-02 08:30:06 -06:00

@Fogapod commented on GitHub (Jun 26, 2022):

"OPTIONS /v2/ HTTP/1.1" 405 0

Do you have CORS enabled in gitea config?

@Fogapod commented on GitHub (Jun 26, 2022): > ``` > "OPTIONS /v2/ HTTP/1.1" 405 0 > ``` Do you have CORS enabled in gitea config?

GiteaMirror commented

2025-11-02 08:30:06 -06:00

@helmut72 commented on GitHub (Jun 26, 2022):

I don't have CORS enabled, then it should be disabled.

@helmut72 commented on GitHub (Jun 26, 2022): I don't have CORS enabled, then it should be disabled.

GiteaMirror commented

2025-11-02 08:30:06 -06:00

@KN4CK3R commented on GitHub (Jun 26, 2022):

I added support for /v2/_catalog and got some problems which prevent a PR but in general it works.
Github/Gitlab may got the same problems which may be the reason they don't provide this endpoint.

@KN4CK3R commented on GitHub (Jun 26, 2022): I added support for `/v2/_catalog` and got some problems which prevent a PR but in general it works. Github/Gitlab may got the same problems which may be the reason they don't provide this endpoint. ![grafik](https://user-images.githubusercontent.com/1666336/175827985-ee3d64d9-cf00-492f-bf10-b218cf88c8ef.png) ![grafik](https://user-images.githubusercontent.com/1666336/175827996-14ad26c8-6963-4fa3-817a-0667c4b04833.png)

GiteaMirror commented

2025-11-02 08:30:06 -06:00

@helmut72 commented on GitHub (Jun 26, 2022):

Wow! But it's up to you. I never used Github/Gitlab registry, just the container image from Docker and I'm used to browse the registry.

@helmut72 commented on GitHub (Jun 26, 2022): Wow! But it's up to you. I never used Github/Gitlab registry, just the container image from Docker and I'm used to browse the registry.

GiteaMirror commented

2025-11-02 08:30:07 -06:00

@KN4CK3R commented on GitHub (Jul 24, 2022):

I have added #20469 but this does not work with Portainer. The _catalog endpoint returns a list like ['owner/image']. Portainer uses this name and requests data from the registry with a call to registry/v2/owner%2Fimage. As you can see Portainer escapes the slash, so that does not work at the moment. Since other tools like docker-ls use the name as is, I would say this a bug in Portainer.

@KN4CK3R commented on GitHub (Jul 24, 2022): I have added #20469 but this does not work with Portainer. The `_catalog` endpoint returns a list like `['owner/image']`. Portainer uses this name and requests data from the registry with a call to `registry/v2/owner%2Fimage`. As you can see Portainer escapes the slash, so that does not work at the moment. Since other tools like `docker-ls` use the name as is, I would say this a bug in Portainer.

GiteaMirror commented

2025-11-02 08:30:07 -06:00

@helmut72 commented on GitHub (Jul 26, 2022):

Wow, thanks! I will create an issue to Portainers repo once your pull request it is included in Gitea.

@helmut72 commented on GitHub (Jul 26, 2022): Wow, thanks! I will create an issue to Portainers repo once your pull request it is included in Gitea.

GiteaMirror commented

2025-11-02 08:30:07 -06:00

@helmut72 commented on GitHub (Mar 26, 2023):

This can be closed as it looks like a problem with Portainer. If Portainer doesn't fix it or won't support Gitea in the future like others, it doesn't matter, because the registry browser in Gitea is an alternative.

@helmut72 commented on GitHub (Mar 26, 2023): This can be closed as it looks like a problem with Portainer. If Portainer doesn't fix it or won't support Gitea in the future like others, it doesn't matter, because the registry browser in Gitea is an alternative.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#9123