billpress
SSH key generation issue with `runpodctl config`
So here's my use case: I'm training models and writing logs to local disk (as well as some trainer models/binaries). Once the training script completes, I need to copy the logs and binaries back to the workflow/user so I can shutdown the pod. I don't want to use a network volume, as I want to be able to grab whatever pod is available of a given type (e.g., H200) anywhere in the country (whereas using a network mounted volume limits the associated pods to the same region).
29 replies
SSH key generation issue with `runpodctl config`
@Dj Is there a plan to fix the ssh keys issue with
runpodctl config
? That would be much simpler from a client perspective, so I can just simply run runpodctl receive <key>
in my workflow and it will all just work.29 replies
SSH key generation issue with `runpodctl config`
@Dj , I still want to run these commands at the end of my container's CMD:
I found the REST API call for stopping the pod. Is there a REST API call you recommend for sending the
/workspace
directory using the $SEND_CODE
(which was generated by the client creating the container, so it can call receive
on its end).29 replies
SSH key generation issue with `runpodctl config`
I did get that error message, but it went away when I created an empty
~/.runpod/config.toml
(by touch
ing it). Then, it worked fine until today, when I started getting this new ssh
-related error.29 replies
Registry auth credential not working
Hi @Dj , I never heard back from you about this. I eventually got the template-based authentication to work; however, I was never able to get logging in with a container registry auth ID (permanent or dynamically created) to work. I don't love using a template, but it'll do for now. Anyway, I appreciated your help here. It's really great to have somebody from RunPod interacting with customers in this way. Thank you.
40 replies
Registry auth credential not working
@Dj I successfully created the container registry auth token from my workflow in the way you recommended (and see it in the portal before it's deleted). Unfortunately, I still continue to get the same error messages in the pod logs. Note that I also set the following now at the top of my workflow job:
40 replies
Registry auth credential not working
Interesting. I had created my own PAT with , but isn't the token associated with my username, since it's my PAT? Will it work with $github.actor when somebody else is running the workflow? I know we're well into GitHub help, vs RunPod help. I really appreciate your support here.
read:packages
and used my username in the container registry auth (that I created using the RunPod UI). I like your flow better, though, creating it dynamically40 replies