knotbin.com knotbin.com requiring login to pull public images is inconsistent with docker hub's behavior and adds a ton of friction to distributing images.
for instance, because tangled knot image is distributed through ATCR, and ATCR requires authentication, I can't deploy tangled knot to my dokploy instance. Also, tangled knot could never add "one click deploy."
But shouldn't the hold itself be the final source of truth for this? I run my own hold which allows public access, but when I try to access it anonymously via atcr.io I still get prompted for authentication.
I understand your point, but when I'm running my own hold the bandwidth is my problem, or am I missing something?
well for pulls, yes there appears to be a bug thats requiring auth even if pulling from a third party hold. for push though, currently the data would have to flow through atcr.io on its way to your hold.
I will fix the issue with public pulls in a future deployment
I've just bumped into this problem myself—did you find where the issue is in allowing anonymous retrieval from my self-hosted hold? I'm happy to help where I can, if that'd be useful!
I’m not sure how to handle these questions. It has been brought up in the past. The code supports anonymous downloads if the operator wants to allow it.
Generally these questions are more directed at my hosted service rather than the code. I don’t currently allow it on my instance because I don’t want unexpected bandwidth cost from randoms. The plan is to eventually allow it, but that’s not going to happen until I can have paid users to offset the costs of this project. Even docker hub rate limits pulls for non authored users.
So to your point, the friction is there purposefully for now. Tangled could host their own, and allow anonymous downloads on their own instance. Any service that allows private registries with a username and password should be able to support it with app-passwords.