[runpodctl] Error creating a pod with a network volume attached
Hi. I am getting an error trying to create a pod with an existing network volume attached. The erroring command:
The same without
--networkVolumeId
successfully creates a pod with a required GPU and all seems well
However it is business-critical to launch a pod with the network volume attached. I can start a pod with the same parameters (secure cloud, network volume attached, RTX4090) without an issue
I tried other combinations (omitting --secureCloud
option, trying with/without templateId
, trying other docker images) - it errors as long as I have networkVolumeId
/volumePath
in the command
What am I missing?1 Reply
Darn, I had a typo in the command 😄
Should use single equals with params, and I had
--networkVolumeId==...
instead
It now works :poddy: