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
{{ message }}
Repository navigation
[Bug]: Dev Environment Fails After ~6 Hours with JOB_FAILED (CONTAINER_EXITED_WITH_ERROR) #2344
I'm experiencing an issue where our dev environment crashes approximately 6 hours after it starts, resulting in a JOB_FAILED (CONTAINER_EXITED_WITH_ERROR) error. This failure occurs even though we haven't specified any idle_duration or max_duration parameter, and we're using spot_policy: on-demand (i.e., it’s not a spot instance issue).
Based on discussions in Discord channel, it seems the environment might be hitting a default maximum duration even though the docs state that max_duration defaults to "off".
Steps to Reproduce:
Apply the dev environment configuration:
dstack apply -f dev.dstack.yaml
(Optional) Detach and reattach to the run:
dstack attach aana-episodic-retrieval-dev
Let the environment run for approximately 6 hours.
Observe the failure:
In dstack Sky, the run shows JOB_FAILED (CONTAINER_EXITED_WITH_ERROR).
The dstack attach session remains active and does not immediately error out.
Actual behaviour
The dev environment terminates around 6 hours after start with the error JOB_FAILED (CONTAINER_EXITED_WITH_ERROR).
The error message is not descriptive enough, as it doesn’t explicitly state that the termination was due to exceeding a maximum duration.
The dstack attach session remains running despite the failure.
Expected behaviour
The dev environment should run indefinitely (or at least without termination after 6 hours) when max_duration is set to off by default or documentation needs to be updated.
If a maximum duration is enforced, the error message should clearly indicate that the termination was due to exceeding the maximum duration.
The dstack attach session should exit when run fails
@movchan74, thanks for the detailed issue. We'll set max_duration to off by default for all run configuration types and ensure dstack attach displays a relevant error message.
Replacing CONTAINER_EXITED_WITH_ERROR with a different error code is currently postponed due to backward compatibility reasons. We'll address this separately.
Activity
r4victor commentedon Feb 24, 2025
@movchan74, thanks for the detailed issue. We'll set
max_durationtooffby default for all run configuration types and ensuredstack attachdisplays a relevant error message.Replacing
CONTAINER_EXITED_WITH_ERRORwith a different error code is currently postponed due to backward compatibility reasons. We'll address this separately.