You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# BACKEND REGION INSTANCE RESOURCES SPOT PRICE
1 tensordock czechrepublic 353c7146-1d73-41ae-b19c-80a578297621 28xCPU, 158GB, 1xA100 (80GB), 158.0GB (disk) no $2.035
Submit a new run? [y/n]: y
shy-ladybug-1 provisioning completed (failed)
All provisioning attempts failed. This is likely due to cloud providers not having enough capacity. Check CLI and server logs for more details.
Expected behaviour
Configuration runs successfully.
dstack version
master
Server logs
[17:43:37] ERROR dstack._internal.server.background.tasks.process_submitted_jobs:380 job(978f83)shy-ladybug-1-0-0: got exception when launching
353c7146-1d73-41ae-b19c-80a578297621 in tensordock/czechrepublic
Traceback (most recent call last):
File "/home/jvstme/git/dstack/dstack/src/dstack/_internal/server/background/tasks/process_submitted_jobs.py", line 359, in
_run_job_on_new_instance
job_provisioning_data = await run_async(
File "/home/jvstme/git/dstack/dstack/src/dstack/_internal/server/utils/common.py", line 24, in run_async
return await asyncio.get_running_loop().run_in_executor(None, func_with_args)
File "/usr/lib64/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/home/jvstme/git/dstack/dstack/src/dstack/_internal/core/backends/tensordock/compute.py", line 123, in run_job
return self.create_instance(instance_offer, instance_config)
File "/home/jvstme/git/dstack/dstack/src/dstack/_internal/core/backends/tensordock/compute.py", line 98, in create_instance
ssh_port={v: k fork, vinresp["port_forwards"].items()}["22"],
KeyError: '22'
Additional information
No response
The text was updated successfully, but these errors were encountered:
Steps to reproduce
Actual behaviour
Expected behaviour
Configuration runs successfully.
dstack version
master
Server logs
Additional information
No response
The text was updated successfully, but these errors were encountered: