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
[10:46:17] DEBUG dstack.api.server:124 POST /api/project/aana/runs/get
DEBUG dstack.api._public.runs:232 Refreshed run aana-episodic-retrieval-dev: RunStatus.PROVISIONING
[10:46:22] DEBUG dstack.api.server:124 POST /api/project/aana/runs/get
[10:46:23] DEBUG dstack.api._public.runs:232 Refreshed run aana-episodic-retrieval-dev: RunStatus.PROVISIONING
[10:46:28] DEBUG dstack.api.server:124 POST /api/project/aana/runs/get
DEBUG dstack.api._public.runs:232 Refreshed run aana-episodic-retrieval-dev: RunStatus.FAILED
aana-episodic-retrieval-dev provisioning completed (failed)
DEBUG dstack.api.server:124 POST /api/project/aana/runs/get
DEBUG dstack.api._public.runs:232 Refreshed run aana-episodic-retrieval-dev: RunStatus.FAILED
Run failed with error code CONTAINER_EXITED_WITH_ERROR.
Check CLI, server, and run logs for more details.
Expected behaviour
The dstack apply command should propagate the error to logs / error column / CLI output
dstack version
Any
Server logs
No response
Additional information
It was quite difficult to troubleshoot the problem as RunPod deleted the pod quickly after the error and we couldn't see the container output. After several attempts, we managed to see the error:
Steps to reproduce
dstack init --token <token>
Actual behaviour
Expected behaviour
The
dstack apply
command should propagate the error to logs / error column / CLI outputdstack version
Any
Server logs
No response
Additional information
It was quite difficult to troubleshoot the problem as RunPod deleted the pod quickly after the error and we couldn't see the container output. After several attempts, we managed to see the error:
The text was updated successfully, but these errors were encountered: