gQsoQa
gQsoQa
RRunPod
Created by gQsoQa on 1/16/2024 in #⛅|pods
Attaching a Network Volume fails when using GraphQL
I have created a Network Volume and would like to start a container with the volume attached. It works without problem in the web UI after clicking the "Deploy" button. However, when using runpod-python's method create_pod, GraphQL endpoint returns the following error: There are no longer any instances available with the requested specifications. Please refresh and try again. (I have tried multiple times) Here is the minimal code:
pod = runpod.create_pod(
"worker",
"myorg/worker:latest",
"NVIDIA GeForce RTX 3070",
network_volume_id=args.network_volume_id,
)
pod = runpod.create_pod(
"worker",
"myorg/worker:latest",
"NVIDIA GeForce RTX 3070",
network_volume_id=args.network_volume_id,
)
args.network_volume_id is probably correct because when I alter it in any way the error message changes to Something went wrong. Please try again later or contact support. The generated GraphQL query looks like this:
mutation {
podFindAndDeployOnDemand(
input: {
name: "worker", imageName: "myorg/worker:latest", gpuTypeId: "NVIDIA GeForce RTX 3070", cloudType: ALL, startSsh: true, supportPublicIp: true, dataCenterId: "EU-RO-1", gpuCount: 1, volumeInGb: 0, containerDiskInGb: 10, minVcpuCount: 1, minMemoryInGb: 1, dockerArgs: "", volumeMountPath: "/runpod-volume", networkVolumeId: "l6y182wxyv"
}
) {
id
desiredStatus
imageName
env
machineId
machine {
podHostId
}
}
}
mutation {
podFindAndDeployOnDemand(
input: {
name: "worker", imageName: "myorg/worker:latest", gpuTypeId: "NVIDIA GeForce RTX 3070", cloudType: ALL, startSsh: true, supportPublicIp: true, dataCenterId: "EU-RO-1", gpuCount: 1, volumeInGb: 0, containerDiskInGb: 10, minVcpuCount: 1, minMemoryInGb: 1, dockerArgs: "", volumeMountPath: "/runpod-volume", networkVolumeId: "l6y182wxyv"
}
) {
id
desiredStatus
imageName
env
machineId
machine {
podHostId
}
}
}
Could you please help me to attach the network volume?
8 replies
RRunPod
Created by gQsoQa on 1/16/2024 in #⛅|pods
Container logs disappear after stopping the container
No description
10 replies