February 26, 20251 yr Just in case anybody missed the memo, the unauthenticated pulls could affect some users, especially if wiping their docker image and then attempting to pull down more than 10 images in a single hour ( a strong possibility) whilst not being authenticated:- No Pull Charges or Limits for Paid Users: Effective immediately, all paid subscriptions will benefit from unlimited pull consumption and unlimited pull rates (within fair use). This change ensures that teams relying on Docker Hub can work without disruptions and enjoy full operational flexibility. Updated Pull Rate Limits for Free/Unauthenticated Users: Unauthenticated users will be limited to 10 pulls per hour. Free authenticated users will have an increased rate of 100 pulls per hour. For those automating processes or requiring a smoother experience, we recommend using Personal or Organizational Access Tokens (PAT & OAT) for seamless integration. Storage Charges Delayed Indefinitely: We have indefinitely postponed the introduction of storage-based billing. Instead, we are developing new management tools to help you actively monitor and control your storage usage. Should storage charges be revisited in the future, we promise to provide at least six months notice so you can plan and adjust accordingly.
February 26, 20251 yr For anybody looking to authenticate docker, right now it's not exposed in the WebUI but is quite straightforward. Create an account on dockerhub. Go to the account settings and generate a read-only Personal Access Token (PAT). Copy the PAT to your clipboard. Open the terminal on Unraid. Type "docker login" Enter your username and press enter. Paste the PAT for the password and press enter. Done. Persists through reboots. PS: You can use Read-Write if you know why you would want one and actively develop containers using your server, but I doubt that would be the case.
February 26, 20251 yr Author 12 hours ago, Xaero said: Done. Persists through reboots. I'm surprised that is persistent, i assume that must be writing your credentials to some location on your USB key then. @SpencerJ Any thoughts on possible inclusion of Docker Hub login via the web ui?, it would be a nice edition and would completely circumvent the issue (100 pulls per hour for authenticated users). EDIT - looks like the authentication token is stored in '/root/.docker/config.json', so for me at least it will not be persistent, so 'go' file is required, output from docker after authenticating:- 'WARNING! Your password will be stored unencrypted in /root/.docker/config.json.'
February 26, 20251 yr 36 minutes ago, binhex said: I'm surprised that is persistent, i assume that must be writing your credentials to some location on your USB key then. @SpencerJ Any thoughts on possible inclusion of Docker Hub login via the web ui?, it would be a nice edition and would completely circumvent the issue (100 pulls per hour for authenticated users). EDIT - looks like the authentication token is stored in '/root/.docker/config.json', so for me at least it will not be persistent, so 'go' file is required, output from docker after authenticating:- 'WARNING! Your password will be stored unencrypted in /root/.docker/config.json.' Above my paygrade. Thoughts @ljm42 and @Squid?
February 27, 20251 yr There was a topic in docker engine about it 7 hours ago, binhex said: EDIT - looks like the authentication token is stored in '/root/.docker/config.json', so for me at least it will not be persistent, so 'go' file is required, output from docker after authenticating:- 'WARNING! Your password will be stored unencrypted in /root/.docker/config.json.' it should not end up there, it should be in /boot/config/plugins/dockerMan/config.json Edit: yeah still the case with 7.0.1 Edited February 27, 20251 yr by Mainfrezzer
February 27, 20251 yr If that's a new feature, a more general communication of the information and the procedure would be good. Not everyone is checking every message in Lounge, and even less for Docker Engine (I know I am not).
February 27, 20251 yr 5 minutes ago, ChatNoir said: If that's a new feature, a more general communication of the information and the procedure would be good. Not everyone is checking every message in Lounge, and even less for Docker Engine (I know I am not). there is no new feature.
February 27, 20251 yr 3 minutes ago, Mainfrezzer said: there is no new feature. I'll rephrase, "if that's something that would become much more relevant now, ... insert the rest of my previous post "
February 27, 20251 yr 1 minute ago, ChatNoir said: I'll rephrase, "if that's something that would become much more relevant now, ... insert the rest of my previous post " I wouldnt say its relevant. Most of the stuff is hosted on both dockerhub and github. Linuxserver, Binhex, Ich777 certainly are huge share of the containers available, the issue are the "3rd-Party" containers. All you can do, for packages that are only available on dockerhub, is go to the dev and ask nicely but firm to push it on github or something else too. Docker has been taking the piss in recent time more and more, first they change Docker to be a firewall service and change the implicit and explicit rules someone set and now they do this crap (which already annoyed people before)
February 27, 20251 yr Author 4 hours ago, Mainfrezzer said: it should not end up there, it should be in /boot/config/plugins/dockerMan/config.json Edit: yeah still the case with 7.0.1 Ahh yeah you are qutie right, the dir is symlinked over to your USB Key (/boot), makes sense.
February 27, 20251 yr Author My last comment on this as it looks like we have a workaround via cli for now, a question that i don't have an answer to yet - Is a no-op pull counted as a pull by Docker Hub?, as in docker image sha on disk matches docker hub image sha, no changes required, if so then if a user clicks on 'check for updates' then unless they have less than 10 containers then this will hit the limit causing subsequent checks to fail, even if there are no updates pending. I am seriously considering switching the registry over to ghcr for all my templates (i push to docker hub, ghcr and redhat quay) but i don't want to do this unless i have to.
February 27, 20251 yr 4 minutes ago, binhex said: My last comment on this as it looks like we have a workaround via cli for now, a question that i don't have an answer to yet - Is a no-op pull counted as a pull by Docker Hub?, as in docker image sha matches docker hub sha, no changes required, if so then if a user clicks on 'check for updates' then unless they have less than 10 containers then this will hit the limit causing subsequent checks to fail, even if there are no updates pending. I am seriously considering switching the registry over to ghcr for all my templates (i push to docker hub, ghcr and redhat quay) but i don't want to do this unless i have to. Thats what they wrote Pull definition A pull is defined as the following: A Docker pull includes both a version check and any download that occurs as a result of the pull. Depending on the client, a docker pull can verify the existence of an image or tag without downloading it by performing a version check. Version checks do not count towards usage pricing. A pull for a normal image makes one pull for a single manifest. A pull for a multi-arch image will count as one pull for each different architecture. https://docs.docker.com/docker-hub/usage/pulls/ i switched the unraid templates to ghcr where it was possible and i know ich777 did the same Edited February 27, 20251 yr by Mainfrezzer
February 27, 20251 yr Author On 2/27/2025 at 9:24 AM, Mainfrezzer said: i switched the unraid templates to ghcr where it was possible and i know ich777 did the same I shall do the same then, obviously that won't stop existing users from still pulling from Docker Hub, but hey at least new users will be pulling from GHCR. EDIT - Completed.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.