deploy fail, can't get template, networking, could not resolve host github.com
I am new to runpod. Have been using same template successfully for two days. I am having OOM errors so I went for a bigger machine, same data center. I changed from L40S to H100SXM. Same data center, TX3. Also I changed from persistent "network volume" to temporary since I always ended up having to recreate every thing anyway. With the L40S I never had to do anything to set up networking. Anybody know why the bigger machine would be giving me a problem getting my template from github? Like I said, I was using it for two days and I still see it out there. https://github.com/Hearmeman24/comfyui-wan/ Thanks for help!
GitHub
GitHub - Hearmeman24/comfyui-wan
Contribute to Hearmeman24/comfyui-wan development by creating an account on GitHub.
6 Replies
can you please clarify what's "setup networking" means
what problem are you experiencing exactly? can you share errors / logs
I should have been more clear. It's in the title: when I try to deploy the new machine on the H100 pod, it fails because it cannot find the template. It cannot find the template because it cannot resolve github.com, where the template is stored. So I concluded that it is a networking problem and I was wondering why, because I have been using the same template for a couple days on an L40S pod in the TX3 data center and I never had to do anything to setup networking on the L40S pod - it retrieved the template from github without me having to do anything to setup networking. "setup networking" means installing networking hardware, drivers, TCP/IP protocol stack and software configuration, hostname, gateway, routes, blah, blah, blah, git, etc, etc, etc, all the stuff one would have to do if one were setting up a physical machine to do these same tasks. @nerdylive Thanks.
Oh you;re using github's registry
oh i see, after you've done that "setup networking" , it works?
what base image did you use?
i just tried on us-tx3 secure cloud, it works ( maybe some machine is affected, you should open a ticket for support to check)
@martinmartyzzz
Escalated To Zendesk
The thread has been escalated to Zendesk!
This is no longer a problem. It worked today on my first try. I have no idea what the problem was the other night but it is gone now. Thanks for your attention.
@Jason There was a ticket opened for this #14913 but I lack the credentials to log in and close it, so to whom it may concern, this ticket may be closed. Thanks! 😃
@Dj