Error response from daemon: container
After uploading my ED25519 SSH, creating a pod (using the "winglian/axolotl-cloud:main-latest image"), and trying to SSH into it, I immediately get a :
error after successfully authenticating to ssh.runpod.io with the public key. Looking at the pod's system logs, it says the image was created, but it doesn't get beyond starting it and the container log shows a "curl: no URL specified" error: I'm trying to run an LLM finetune using axolotl
error after successfully authenticating to ssh.runpod.io with the public key. Looking at the pod's system logs, it says the image was created, but it doesn't get beyond starting it and the container log shows a "curl: no URL specified" error: I'm trying to run an LLM finetune using axolotl
Solution:
Jump to solution
Quick update, this is due to the template in the tutorial no longer being maintained as the repo for git moved under axolotl.
The working RunPod Template for this is axolotali/axolotl-cloud:main-latest
And currently the axolotlai template is working. I have raised this issue internally with our team and we will get the template in the tutorial updated to point to this as well....
13 Replies
Eh I kind kf don't get it, is the error response from daemon container or this curl command
If it's just the curl command then it's because the curl command arguments isn't valid
The (--paramname ) thing
This error is in response from me starting the pod and from the curl command executed from within the starting pod. All I did was start the pod. Is that not supposed to work straight out of the box?
What template did you use?
Does your docker image works with that command?
I used LazyAxolotl (winglian/axolotl-cloud:main-latest)
Fine tune an LLM with Axolotl on RunPod | RunPod Documentation
Learn how to fine-tune large language models with Axolotl on RunPod, a streamlined workflow for configuring and training AI models with GPU resources, and explore examples for LLaMA2, Gemma, LLaMA3, and Jamba.
All I'm trying to do is launch an axolotl run once I can get into the server, send my files over, etc.
I see, did you set any environment variable or anything that's need to be configured here it seems like it says no specified url
I can try it like tommorow to follow that and check if you want or you wanna ask staff in a ticket
@!Xabbu
Escalated To Zendesk
The thread has been escalated to Zendesk!
I just created a volume in a region, picked a GPU, selected # of GPUs, and started the pod with that image/template
I would appreciate that
curl command is coming from Container Start Command in this Template, its trying to call an ENV VAR called $SCRIPT which does not exist on this image while running it locally.
I would expect to see an env var from the command printenv | grep SCRIPT but there is nothing. Not a single mention of a URL in env.
Remove the Container start command by Editing the Pod and the container should start and be accessible, as it stops the container from continually looping. You can also keep a container from looping by adding bash -c ‘sleep infinity’ to the container start command.
As once the command finishes, it will just restart the pod unless its told to stay up.
https://github.com/axolotl-ai-cloud/axolotl
Solution
Quick update, this is due to the template in the tutorial no longer being maintained as the repo for git moved under axolotl.
The working RunPod Template for this is axolotali/axolotl-cloud:main-latest
And currently the axolotlai template is working. I have raised this issue internally with our team and we will get the template in the tutorial updated to point to this as well.
Excellent. Thanks. I will give the other template a try.
I was able to stand up the pod with this change. Thanks