imageName required for runpodctl create pod

[cloud sandal]

I am trying to start a pod with a custom template and network storage. Id's are set correctly and it deploys fine via the website. Via the CLI however, I get this error: Error: There are no longer any instances available with the requested specifications. Please refresh and try again.. Here is the command I am using: runpodctl create pod --networkVolumeId "fpomddpaq0" --gpuType "L40" --imageName "runpod/pytorch:2.1.1-py3.10-cuda12.1.1-devel-ubuntu22.04" --secureCloud I have tried several gpu types. I dont understand why imageName is required: Error: required flag(s) "imageName" not set when I have set a template?

[empty spoke]

Raised this internally

[cloud sandal]

any update on this?

[cloud sandal]

I did some testing with graphql

For this input:

{
  "input": {
    "cloudType": "ALL",
    "gpuCount": 1,
    "gpuTypeId": "NVIDIA L40",
    "volumeInGb": 40,
    "containerDiskInGb": 40,
    "minVcpuCount": 2,
    "minMemoryInGb": 15,
    "name": "RunPod Test Pod",
    "imageName": "runpod/pytorch:2.1.1-py3.10-cuda12.1.1-devel-ubuntu22.04",
    "dockerArgs": "",
    "ports": "8888/http,22/tcp",
    "volumeMountPath": "/workspace",
    "startJupyter": False,
    "startSsh": True,
    "supportPublicIp": True,
    "templateId": "8wwnezvz5k",
    "networkVolumeId": "fpomddpaq0",
  }
}

Output:

Deployment Response: {'errors': [{'message': 'Something went wrong. Please try again later or contact support.', 'locations': [{'line': 12, 'column': 5}], 'path': ['podFindAndDeployOnDemand', 'gpus'], 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}], 'data': {'podFindAndDeployOnDemand': None}}

For this input:

{
  "input": {
    "cloudType": "SECURE",
    "gpuCount": 1,
    "gpuTypeId": "NVIDIA L40",
    "cloudType": "SECURE",
    "networkVolumeId": "fpomddpaq0",
    "ports": "8888/http,22/tcp",
    "startJupyter": False,
    "startSsh": True,
    "supportPublicIp": True,
    "templateId": "8wwnezvz5k",
  }
}

Output:

Deployment Response: {'errors': [{'message': 'There are no longer any instances available with enough disk space.', 'path': ['podFindAndDeployOnDemand'], 'extensions': {'code': 'RUNPOD'}}], 'data': {'podFindAndDeployOnDemand': None}}

[idle pendant]

Your request is wrong, you need data center id when specifying network volume id

[empty spoke]

Unfortunately not, will ask again

[idle pendant]

You have to provide data center id for all of them, graphql as well as runpodctl, they all work fine, there is no issue here, the user is wrong.

You can't specify network storage id without data center id.

[cloud sandal]

It worked even though I was returned those error messages. Those pods have been running for 2 hours now and have drained my account...

I think there was also a delay in initialization

[cloud sandal]

same error: Deployment Response: {'errors': [{'message': 'Something went wrong. Please try again later or contact support.', 'locations': [{'line': 7, 'column': 5}], 'path': ['podFindAndDeployOnDemand', 'gpus'], 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}], 'data': {'podFindAndDeployOnDemand': None}}

[cloud sandal]

I can now see that with this input it immediately creates a pod and returns 500. I added the datacenter id for good measure

[idle pendant]

Wow it shouldn't create a pod if it has an internal server error, thats terrible 😱

[empty spoke]

cc: @copper token

[empty spoke]

Check your DMs

[cloud sandal]

I think I found the problem, it's one of these in the podFindAndDeployOnDemand mutation:

gpuCount
gpus {
    id
}
ports
templateId
networkVolumeId