fmartinou
[Bug?] Attempting to use *public* (unauthenticated) registries results in 401
I have a container that uses code.forgejo.org, public access, but the registry wasn't recognized so I had to create a custom one (without authentication). While WUD recognizes the image as belonging to the repository it returns a 401 under the expectation there's supposed to be login information despite there not needing to be to pull (for example: code.forgejo.org/forgejo/forgejo:13-rootless).
The Gitea, where forgejo is build on, code, does not support anonymous/non-login I think. So that would explain your issues
The Gitea, where forgejo is build on, code, does not support anonymous/non-login I think. So that would explain your issues
I can docker pull image from my Forgejo instance anonymously on my own machine. (Edit: And anyone can pull from Codeberg anonymously, I do it for the Forgejo instance.)
The Gitea, where forgejo is build on, code, does not support anonymous/non-login I think. So that would explain your issues
I can
docker pull imagefrom my Forgejo instance anonymously on my own machine. (Edit: And anyone can pull from Codeberg anonymously, I do it for the Forgejo instance.)
Again, I just explained what is wrong with the code. You dont have to repeat yourself, when someone just confirms your bugs report.
The Gitea, where forgejo is build on, code, does not support anonymous/non-login I think. So that would explain your issues
I can
docker pull imagefrom my Forgejo instance anonymously on my own machine. (Edit: And anyone can pull from Codeberg anonymously, I do it for the Forgejo instance.)Again, I just explained what is wrong with the code. You dont have to repeat yourself, when someone just confirms your bugs report.
I read it as "it's Gitea/Forgejo's fault", so it didn't sound like it confirmed it.