February 21, 20251 yr https://docs.docker.com/docker-hub/usage/ tldr; 10 pulls an hour unauthenticated. Can we get fields on docker settings page to input authentication information?
February 21, 20251 yr Community Expert 13 minutes ago, DiscoverIt said: https://docs.docker.com/docker-hub/usage/ tldr; 10 pulls an hour unauthenticated. Can we get fields on docker settings page to input authentication information? open the terminal and type "docker login" the ui uses the information. (well, it would be a surprise if it wouldnt, cause its the docker daemon doing things after all. the repository logins are all stored on /boot/config/plugins/dockerMan/config.json) Edited February 21, 20251 yr by Mainfrezzer
February 21, 20251 yr Author That is a workaround indeed. However a permanent fix should be discussed since Unraid is tailored for new Linux users and docker is a key feature pillar.
February 21, 20251 yr Community Expert 3 minutes ago, DiscoverIt said: That is a workaround indeed. However a permanent fix should be discussed since Unraid is tailored for new Linux users and docker is a key feature pillar. What do you mean, workaround? This is permanent. Your credentials are used unless you use docker logout or delete the file. If you, have a need to create a dockerhub account, or even a github account, you can resonably expect to type 2 words (3 for github) into the terminal.
February 21, 20251 yr Author Pushing a new user into command line is not a valid solution. The problem is this new change will impact most new unraid install roll out. Edited February 21, 20251 yr by DiscoverIt
February 21, 20251 yr Community Expert Just now, DiscoverIt said: Pushing a new user into command line is not a valid solution. The problem is this new change will impact nearly every new unraid install roll out. While i agree, pushing people to sign up on dockerhub is also not a valid solution
February 21, 20251 yr Author What’s the fix then? One cannot force all development of container images off DockerHub. While some have moved to GHCR the vast majority of still valid images reside on DockerHub.
February 21, 20251 yr It is a simple solution, in the next version of unraid we will incorporate in the docker tab an option to enter dockerhub as anonymous (like now) or by entering your credentials, with that you go from 10 requests per hour to 40 per hour.
February 21, 20251 yr 9 hours ago, Mainfrezzer said: open the terminal and type "docker login" the ui uses the information. (well, it would be a surprise if it wouldnt, cause its the docker daemon doing things after all. the repository logins are all stored on /boot/config/plugins/dockerMan/config.json) does that persist past reboot?
February 21, 20251 yr Community Expert 6 minutes ago, bhcompy said: does that persist past reboot? yes, as stated, it saves the repository login information on the flash drive, at /boot/config/plugins/dockerMan/config.json (thats the file thats usually at ~/.docker/config.json)
February 22, 20251 yr I agree this probably should be addressed via the WebUI. Ideally, using Personal Access Tokens - since they won't allow login to the user's docker account, or any other accounts, if compromised.
February 22, 20251 yr Here, the one who may have problems from April 1, 2025 is on the one hand the one who messes around a lot with docker and those 10 pulls are eaten in nothing or the one who has many dockers and many automated updates, we are already facing a person who knows what a docker login is, in that case until there is a solution in the web interface by unraid the best solution is: 1. Go to your dockerhub account and in Account Settings -> Personal access tokens and generate a new token without expiration date and with read-only access (to mitigate problems). 2. Once the previous step is done, follow the instructions that it gives us, which is basically in the unraid terminal: docker login -u <user_dockerhub> And in password the generated token. Ready, you already have 100 pulls/h.
June 29, 20251 yr Following up a couple months later - I hit the limit today, and I followed this procedure and can confirm my PAT is saved where expected - but I'm still being throttled. Does this require a reboot on 7.1.4 in order for dockerMan to use it?
May 23May 23 As a possible alternative to docker login which was being flaky on my unraid and still hitting limit after successful login.(supposedly 100 pulls for anonymous and 200 for authenticated : timer reset every 6 hours)I found using a mirror alleviated dockerhub rate block.edit /etc/docker/daemon.json and add: "registry-mirrors": ["https://grc.io"]Here's how mine looked:cat /etc/docker/daemon.json { "runtimes": { "nvidia": { "path": "/usr/bin/nvidia-container-runtime", "runtimeArgs": [] } }, "registry-mirrors": ["https://grc.io"]}Note that mirror availability can change; it is best to verify they are active before production use.
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.