This message was deleted.
# rancher-desktop
a
This message was deleted.
w
error?
c
Trying to get around the joy that is docker hub rate limit. Ends up being an imageerrpull
I have a work around but was curious if others had seen this before 🤷
w
well if its rate limiting it will be hard to get away from since its chicken and egg with auth
c
So on command line you can nerdctl login with a users docker hub account and pull the images.
w
the login handler seems to work fine for me in a host based terminal. no need to do anything in alpine… just docker login registry-1.docker.io
nerdctl private registry i swore had an issue need to test that
c
Yeah no issues there was trying to get the rancher desktop container runtime logged in
w
actually just worked for me so no issues there
c
Did you do it from the Lima vm??? And it respected it?
w
nope from the host. using the shim. you shouldn’t need to use rdctl shell for most things
c
What is this shim you speak of?
I'm a novice with the tool kinda started today 🤣
w
the nerdctl binary you see in ~/.rd/bin
or in the windows location that escapes me for the moment
c
Hmm I did indeed do that from the host and have that in my path
w
%LOCALAPPDATA%\rancher-desktop\bin or something like that
c
So on the host nerdctl pulls fine with my login. But if I deploy a pod say nginx the k3s instance doesn't appear to respect that login
w
ahh yeah def a difference between docker and k8s
c
That was my work around for now to pull on the host using nerdctl, but would be nice to save the step and just let k3s do that
w
did you create the pull secret in k8s and then patch the service account to use that?
c
Oh no haven't tried that let me give it a whirl (1st have to have multiple people hammer the same image anonymously 🤣)
w
yeah k8s won’t use your client secret so you need to go that direction to create a pull secret and if all your pulls should hit that registry consider patching the serviceacct if you are lazy like me
👍 1
c
Much appreciated thanks for the assistance