Stop or Delete a Workspace
Stop a workspace
Stopping pauses a workspace so it stops using CPU and memory. Depending on the provider, Devsy stops the container or shuts down the VM it runs on. Workspace data is kept unless the provider discards disk state on shutdown, as microsandbox does with ephemeral enabled.
In Devsy Desktop, open the workspace actions menu and choose Stop. From the CLI, run:
devsy workspace stop my-workspaceTo start it again, run:
devsy workspace up my-workspaceSome providers stop idle workspaces on their own. See Auto-inactivity timeout.
Stopping or deleting a workspace first cancels its running devsy workspace up --detach task. To cancel a task yourself, run devsy workspace task cancel <task-id>.
Delete a workspace
Deleting removes the workspace and its local workspace data. Depending on the provider, Devsy removes the container or deletes the VM. Build and lifecycle output in setup history stays in the local store until retention prunes it.
In Devsy Desktop, open the workspace actions menu, choose Delete, and confirm. If the delete fails, the workspace detail page shows the error and links to the logs.
From the CLI, run:
devsy workspace delete my-workspacedevsy workspace down and devsy workspace rm are aliases for the same command.
If the provider is unreachable, force the delete:
devsy workspace delete my-workspace --forceWith --force, Devsy continues past several teardown errors:
- Container deletion, including machine providers without
autoDelete: Devsy ignores a failed container teardown and logs errors other than a deadline timeout. If Devsy cannot check the machine status, it skips the container teardown. - Auto-delete machines: Devsy logs a failed machine delete command and continues.
- Daemon-backed workspaces: Devsy still tries to delete the instance. It logs delete request errors other than NotFound and continues. Waiting for deletion can still return an error.
Provider resources can remain after a forced delete.