Pod ssh configuration docs out of date?

I've been having issues setting up ssh for new pods using the current documentation. After some investigation, it looks like the ssh pub key environment variable has changed names from

RUNPOD_SSH_PUBLIC_KEY

RUNPOD_SSH_PUBLIC_KEY

PUBLIC_KEY

PUBLIC_KEY

.

I ran the following script as a startup command to discover:

bash -c 'echo "Listing all environment variables:"; env | cut -d= -f1 | sort; echo "Searching for likely SSH public key variables:"; env | grep -i "ssh\|key\|pub" || echo "No matching variables found"; sleep infinity'

bash -c 'echo "Listing all environment variables:"; env | cut -d= -f1 | sort; echo "Searching for likely SSH public key variables:"; env | grep -i "ssh\|key\|pub" || echo "No matching variables found"; sleep infinity'

and got the following:

2024-07-02T08:21:36.097917026Z Searching for likely SSH public key variables:
2024-07-02T08:21:36.099944648Z RUNPOD_PUBLIC_IP=xxx
2024-07-02T08:21:36.099960728Z RUNPOD_API_KEY=yyy
2024-07-02T08:21:36.099964999Z PUBLIC_KEY=zzz

2024-07-02T08:21:36.097917026Z Searching for likely SSH public key variables:
2024-07-02T08:21:36.099944648Z RUNPOD_PUBLIC_IP=xxx
2024-07-02T08:21:36.099960728Z RUNPOD_API_KEY=yyy
2024-07-02T08:21:36.099964999Z PUBLIC_KEY=zzz

Simply updating the recommended startup script to use

$PUBLIC_KEY

$PUBLIC_KEY

instead of

$RUNPOD_SSH_PUBLIC_KEY

$RUNPOD_SSH_PUBLIC_KEY

resolved the issue. I would also recommend adding some extra logging as the current script fails silently. I have a branch with the updates ready but looks as though I can't pull request into the repo.

Runpod•2y ago•

5 replies

yoni

Pod ssh configuration docs out of date?

I've been having issues setting up ssh for new pods using the current documentation. After some investigation, it looks like the ssh pub key environment variable has changed names from

RUNPOD_SSH_PUBLIC_KEY

RUNPOD_SSH_PUBLIC_KEY

PUBLIC_KEY

PUBLIC_KEY

.

I ran the following script as a startup command to discover:

bash -c 'echo "Listing all environment variables:"; env | cut -d= -f1 | sort; echo "Searching for likely SSH public key variables:"; env | grep -i "ssh\|key\|pub" || echo "No matching variables found"; sleep infinity'

bash -c 'echo "Listing all environment variables:"; env | cut -d= -f1 | sort; echo "Searching for likely SSH public key variables:"; env | grep -i "ssh\|key\|pub" || echo "No matching variables found"; sleep infinity'

and got the following:

2024-07-02T08:21:36.097917026Z Searching for likely SSH public key variables:
2024-07-02T08:21:36.099944648Z RUNPOD_PUBLIC_IP=xxx
2024-07-02T08:21:36.099960728Z RUNPOD_API_KEY=yyy
2024-07-02T08:21:36.099964999Z PUBLIC_KEY=zzz

2024-07-02T08:21:36.097917026Z Searching for likely SSH public key variables:
2024-07-02T08:21:36.099944648Z RUNPOD_PUBLIC_IP=xxx
2024-07-02T08:21:36.099960728Z RUNPOD_API_KEY=yyy
2024-07-02T08:21:36.099964999Z PUBLIC_KEY=zzz

Simply updating the recommended startup script to use

$PUBLIC_KEY

$PUBLIC_KEY

instead of

$RUNPOD_SSH_PUBLIC_KEY

$RUNPOD_SSH_PUBLIC_KEY

Pod ssh configuration docs out of date?

Similar Threads

Pod ssh configuration docs out of date?

Similar Threads

Similar Threads

Similar Threads