/usr/bin/bash: cannot execute binary file
I'm trying to set up custom template with my own container image. When I try to set up SSH according to docs (https://docs.runpod.io/pods/configuration/use-ssh) I get errors on container start:
2024-02-18T17:40:55.341955276Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
2024-02-18T17:41:11.745017647Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
2024-02-18T17:41:28.059617609Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
2024-02-18T17:41:44.387377159Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
2024-02-18T17:42:00.764592909Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
2024-02-18T17:42:17.092566318Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
2024-02-18T17:40:55.341955276Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
2024-02-18T17:41:11.745017647Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
2024-02-18T17:41:28.059617609Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
2024-02-18T17:41:44.387377159Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
2024-02-18T17:42:00.764592909Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
2024-02-18T17:42:17.092566318Z /usr/bin/bash: /usr/bin/bash: cannot execute binary file
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.
