SCP
scp -P 22 -i ~/.ssh/id_ed25519 root@213.173.102.159:/mmdetection/data/results/vis/results.tar.gz ./
root@213.173.102.159's password:
I am attempting to retrieve some files from my pod via SCP but I'm being prompted for a password, why is this happening?
Solution:Jump to solution
Yep absolutely correct, I ended up solving it with: bash -c 'apt update;DEBIANFRONTEND=noninteractive apt-get install openssh-server -y;mkdir -p ~/.ssh;cd $;chmod 700 ~/.ssh;echo "$PUBLIC_KEY" >> authorized_keys;chmod 700 authorized_keys;service ssh start;sleep infinity' as my docker command and was going to update my post but couldn't find where my post was in help-topics (turns out it was in serveless lol)
10 Replies
@arken What could be happening is that the public key is not in the runpod public key section. BTW I assume this is for GPU pod even though you are in serverless section rn.
RunPod
Use Real SSH
The basic terminal SSH access that RunPod exposes is not a full SSH connection and, therefore, does not support commands like SCP. If you want to have full SSH capabilities, then you will need to rent an instance that has public IP support and run a full SSH daemon in your Pod.Setup Generate your pu...
I was able to reproduce this just now, where I did
https://discord.com/channels/912829806415085598/1194711850223415348/1194711850223415348
But I kept getting a password prompt. SO I went to my other computer, where I had written the guide and it worked. Then I realized, OH. My public key is not inside of runpod pod.
You can grab your public key and paste it in like the article. Or if you followed my resource, it should have injected it into your settings ssh public key. Which you can then copy that public key, and manually copy that into your pod since the public key was created after the pod was initialized.
I could be wrong, just my best guess
Solution
Yep absolutely correct, I ended up solving it with: bash -c 'apt update;DEBIANFRONTEND=noninteractive apt-get install openssh-server -y;mkdir -p ~/.ssh;cd $;chmod 700 ~/.ssh;echo "$PUBLIC_KEY" >> authorized_keys;chmod 700 authorized_keys;service ssh start;sleep infinity' as my docker command and was going to update my post but couldn't find where my post was in help-topics (turns out it was in serveless lol)
Appreciate the answer!
@arken Please log things under the correct section in future. This is for GPU Cloud not for Serverless.
might want to change the last message in the archived general chat - I just mindlessly clicked it and created a post and I don't see why a general chat should point to a specific help channel like serverless
Yeah that message is wrong, I can see how it can be confusing (cc: @Polar ) There is #⛅｜gpu-cloud for logging issues with GPU cloud and #🎤｜general for general discussion/queries.