Open vedranjukic opened 5 months ago
Just a reproduction note. This can also be achieved if the user uses the Docker provider and stops the project container with the Docker CLI (not with daytona stop
).
The same applies to all providers. If the user manages the resources without going through Daytona, state will fall out of sync and we should address that.
Describe the bug The workspace state is not updated after the Docker host machine running the workspaces is restarted. This exposes the issue of handling the workspace state that must be revisited.
To Reproduce Steps to reproduce the behavior:
running
but the container isstopped
.Expected behavior The workspace state should show
stopped
.