generativelabs/runpod-worker-a1111 broken
error pulling image: Error response from daemon: pull access denied for generativelabs/runpod-worker-a1111, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
47 Replies
im getting this error on the runpod serverless for the a1111, but only on certain workers that are initializing, any thoughts why?
That is the message you get when you try to pull a docker image that is either removed from the repository or made private by the owner.
yeah but this is the official one from runpod supposedly generativelabs/runpod-worker-a1111
since the one we were using before got deleted
What makes it official?
but the thing is sometimes it works
it was listed here in this serverless channel as the official replacement for it
i mean i made a clone of it but i dont think its the serverless because some workers can use it just fine
If it was just removed from the repo, it could take time to vanish from any caches.. so it could vary depending on RunPod region.
ohhh
I just search DockerHub and it is not there.
hmmm
GitHub
GitHub - generativelabs/runpod-worker-a1111
Contribute to generativelabs/runpod-worker-a1111 development by creating an account on GitHub.
this is the github
I suggest clone that immediatly, maybe you can rebuild it from that source.
I am so jaded from this stuff I only trust images that I built and have control of the image... otherwise it is just a matter of time until it stops working or is unavailable. 😦
i cloned that github but i dont know how to build it into the docker hub ;-;
Ohh I see the problem, that github page describes you have to do this command to build this:
I have found previously that ALL ashleykleynhans images/github was removed. So, it is impossible to rebuild this. Sorry 😦
yeah
i was using ashley's
I ran into the same issue with LLava
then this was the replacement for ashleys
now its showing as broken
or at least partially broken
Yeah... seems ashleykleynhans closed their github and Docker hub account and pulled everything... NO reason why but it has been super annoying.
im sure the person that built this is from runpod https://github.com/generativelabs/runpod-worker-a1111
GitHub
GitHub - generativelabs/runpod-worker-a1111
Contribute to generativelabs/runpod-worker-a1111 development by creating an account on GitHub.
so we can get a dockerhub built too
Even if that is true, they built it based upon ashleykleynhans and that no longer exists...
is it that hard to build the docker tho
# Clone the repo
git clone https://github.com/ashleykleynhans/runpod-worker-a1111.git
cd runpod-worker-a1111
# Build and push
docker build -t dockerhub-username/runpod-worker-a1111:1.0.0 .
docker login
docker push dockerhub-username/runpod-worker-a1111:1.0.0
instead of gitclone on ashley just do it on copied git?Nope, it is gone. 100% completely no longer present.
If before it was removed, you pulled the image onto a system you control.. you might be able to push it to a repo and use that still.
Or if you cloned the Github, before it was removed, you could build it once again from that source.
Sorry I know these are not great options. 😦
this is the same as ashley's tho https://github.com/generativelabs/runpod-worker-a1111
GitHub
GitHub - generativelabs/runpod-worker-a1111
Contribute to generativelabs/runpod-worker-a1111 development by creating an account on GitHub.
You could build the generativelabs/runpod-worker-a1111 image from that source if you could finish this command:
But, since that .git is is missing. You cannot.
generativelabs/runpod-worker-a1111 DEPENDS on ashleykleynhans/runpod-worker-a1111.git
It seems you do not like this answer, so I will bow out and see if anyone else can provide you with an alternative solution.
:sad_cat:
ok i figured it out, wasnt able to build a docker properly but i found someone else that built one 10 days ago
https://github.com/daswer123/runpod-worker-a1111
docker container: daswer123/runpod-worker-a1111:1.2
cloned it and pushed to my personal docker hub :Wavey:
confirmed it works and now we should be gud
Suggest that you push image to a repo you control... then you will have this image no matter what happens in the future. You can host unlimited private repos(images) on Docker hub for $7/month.
yeah i did that, its a public one tho, and i think its free
yes public is free 🙂
i need it to be public anyways because i have to tell the runpod serverless to pull it
its in my dockerhub account now tho
the image
lol
so i should be good right
like nobody can take it offline from my own docker hub
That is one option... or you can provide the docker key and use private repos.
ohh
right
just an example
ooo
i never looked at that box lol
To setup new repo credentials at Settings / Container Registry Auth
why private so good?
What do you mean private so good
It depends on your circumstance. Just giving you all your options. As long as you control the repo, public or private, you should avoid loosing access to it.
hi, I've deployed that docker image and this error occurs.
any good person can help me?
it happens during installation from automatic script https://github.com/generativelabs/runpod-worker-a1111/blob/main/docs/installing.md
GitHub
runpod-worker-a1111/docs/installing.md at main · generativelabs/run...
Contribute to generativelabs/runpod-worker-a1111 development by creating an account on GitHub.
:/
yeah i dunno, i install it piece by piece
i will try...