gQsoQa
gQsoQa
PostsComments
RRunPod
Created by gQsoQa on 1/16/2024 in #⛅｜pods
Attaching a Network Volume fails when using GraphQL
I think I've identified the issue, thanks again for your help! First of all, cloudType: SECURE was needed as you suggested. After that, the error was not caused by the network volume but rather by the GPU (unfortunately the error message is quite vague). This happened because runpod-python automatically sets dataCenterId to the datacenter of the network volume, which is different than my default. This means that attaching the volume changed the datacenter to a different one where the concrete GPU was not available.
8 replies
RRunPod
Created by gQsoQa on 1/16/2024 in #⛅｜pods
Attaching a Network Volume fails when using GraphQL
Thank you for your response! I changed cloudType to SECURE and removed the volumeInGb field, but the error message still stays the same. The query now looks like this: 
mutation {
      podFindAndDeployOnDemand(
        input: {
          name: "worker", imageName: "myorg/worker:latest", gpuTypeId: "NVIDIA GeForce RTX 3070", cloudType: SECURE, startSsh: true, supportPublicIp: true, dataCenterId: "EU-CZ-1", gpuCount: 1, 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: SECURE, startSsh: true, supportPublicIp: true, dataCenterId: "EU-CZ-1", gpuCount: 1, containerDiskInGb: 10, minVcpuCount: 1, minMemoryInGb: 1, dockerArgs: "", volumeMountPath: "/runpod-volume", networkVolumeId: "l6y182wxyv"
        }
      ) {
        id
        desiredStatus
        imageName
        env
        machineId
        machine {
          podHostId
        }
      }
    }
Deploying without the network volume (omitting the network_volume_id parameter) works fine.
8 replies
RRunPod
Created by gQsoQa on 1/16/2024 in #⛅｜pods
Container logs disappear after stopping the container
Thank you!
10 replies
RRunPod
Created by gQsoQa on 1/16/2024 in #⛅｜pods
Container logs disappear after stopping the container
How can I access the logs programmatically so that I can push them to another service like you recommend?
10 replies