Empty Root - No workspace on Exposed TCP Connection
I have just created a connection over exposed tcp for the first time and finally got to ssh into my machine. However when I ls my actual installlation, nothing is there. It is frustrating as I am used to the "workspace" folder that is needed in order to save files between uses of the machine. Did I miss something in the setup, or is this how it is supposed to be?
5 Replies
Just run the cd command to your /workspace
It's mounted there
It's all supposed to be that way, your last workdir command on dockerfile will be your default path when logon with ssh
there is no directory /workspace
when I get to my computer again I'll show u,
okay, so it turns out I set up my runpod wrong, thank you so much for helping!
And yes, now that I changed the way I set it up I need to cd /workspace.
I really appreciate it.
Ooh alright your welcome
You would need to use network storage.
yeah I figured
I'm not exactly sure tho how that works, ill read docs probably and find it out