Repository navigation
feat(tui): recreate a workspace container - #47
Merged
Mickael-Roger merged 3 commits intoSep 27, 2026
Merged
Conversation
Add an `r` action that removes the selected workspace's container and starts a fresh one from the current workspace image, keeping the workspace. The host-mounted home survives and module reconciliation reinstalls modules, so a container left broken (e.g. by an interrupted update) no longer needs a manual `podman rm` followed by a start. Like an update, it is refused while an agent is working or waiting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
|
Fixed the review findings: only Recreate completion clears its lock; start/stop/delete are blocked during recreation, and regression tests cover unrelated completions and conflicting actions. Recovery now reuses the cached workspace image without pulling or rebuilding the base. If the workspace image is missing, recovery fails before removing the existing container. Added regression coverage for a pruned base and a missing workspace image. Validation: go test ./... and go vet ./... passed; gofmt and git diff --check clean. Docker/Podman integration was not run locally because neither runtime is installed. |
# Conflicts: # internal/workspace/lifecycle.go
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When a workspace container ends up broken (for example after an interrupted base-image update), the only way to recover was to
podman rm/docker rmit by hand and then start the workspace again.This adds an
r(recreate) action to the TUI that removes the selected workspace's container and starts a fresh one from the current workspace image, keeping the workspace:uremains the way to update the image.u, and while an update or recreate of the same workspace is already running.recreatingwhile it runs.Lifecycle.RecreateContainer; listed in the key menu,?help, anddocs/tui.md.Testing
go vet ./...andgo test ./...pass; new tests cover the lifecycle (remove → create → start, manifest kept, no pull) and the TUI gating/status.🤖 Generated with Claude Code