RunpodR
Runpod2y ago
5 replies
papanton

Container start command behavior

I am starting a serverless container using image: runpod/pytorch:2.2.0-py3.10-cuda12.1.1-devel-ubuntu22.04

On the start command I am adding: mv /runpod-volume /workspace && bash /workspace/runpod/pod-startup.sh

I exepct the runpod-volume to be renamed to workspace and then run the script, but instead this is what I get:


2024-02-08T00:28:01.115082438Z mv: target '/workspace/runpod/pod-startup.sh' is not a directory
Solution
@papanton Not familiar with what ur trying to do but maybe try to use a symlink instead
Was this page helpful?