Stuck in creating container
No matter how I had set up the pod, it would be stuck in starting container, dozens, 20, times.
Then I saw that it was choosing the "location" I left as any because I dont really care. Turns out, it was always redirecting to a specific place and not starting.
I tried manually choose the location, and turned out no matter which option on the available setup I had chosen, they were only working part creating container on TX. But then get stuck in "image pull pending". At least on the TX, it did not pretended to run and consumed my credit without actually running.
Still, not running at all.
3 Replies
What do you see in the logs?
Just "image pull pending"?
I was, yes. But I decided to change the image and use it only to train the models on the Bloke template, and leave it at that. Wont be worrying too much as I am trying this service, but I can do a lot of it locally at a slower pace. It does not seem to be working so far for Stable Diffusion model as well. Work I have done fine in my local deployment are filling with errors in the template offered in runpod as well. Chuck it on the "yeah, right" box. And I am done. Guess counts as "cost of knowing it doesnt work".
Rich templates were you using? Were they custom ones you created or existing ones?