Specifying a Template ID on "create_pod" will cause QueryError: There are no longer any instances available with enough disk space.

[ChristophEndruschat]

Describe the bug
Whenever I try to start a pod over runpod-python specifying a custom template ID I will get the message: "runpod.error.QueryError: There are no longer any instances available with enough disk space."

• This happens for every custom template I tested it on. I was not able to test this on public templates, as I don't know how to find the template IDs for these.
• This does not happen, when I start the exact same template manually over the website.
• Using an invalid template_id will also cause the same error, but should indicate that the template_id is invalid, because problem is not disk space as message says.

This works as expected:
runpod.create_pod("test-pod-1", "dhiaeddine23/alphapedia-app:v-1.0.12", "NVIDIA RTX A4000", cloud_type="COMMUNITY")

But this never works:
runpod.create_pod("test-pod-1", "dhiaeddine23/alphapedia-app:v-1.0.12", "NVIDIA RTX A4000", cloud_type="COMMUNITY", template_id="ppny3n7iri")

To Reproduce
Steps to reproduce the behavior:

1. Import runpod-python package
2. Set runpod.api_key for account
3. Create custom template on that account
4. Run runpod.create_pod using the custom template_id

Expected behavior
RunPod should find the template by ID on my user account, then apply all parameters saved in the template to the pod created by the create_pod function.

Screenshots
Here is my template with the ID on the website:

And here the template configuration:

Desktop:

• OS: Windows 11
• Browser: Chrome (121.0.6167.161)

[cendruschat]

Any solution in sight?

[jaredsu]

Specify the amount of gb in the container disk and it should work. Should look like this
runpod.create_pod("test-pod-1", "dhiaeddine23/alphapedia-app:v-1.0.12", "NVIDIA RTX A4000", container_disk_in_gb=20, cloud_type="COMMUNITY", template_id="ppny3n7iri")

[tdi]

I confitm @jaredsu's sugestion. I stumbled upon the same problem. You need to give it at least some space. Also @justinmerrell why is there a need to specify image if it is specified in template ? I suggest maybe a new method
create_pod_from_template where we prefill some of the fields from template already ?