-
Notifications
You must be signed in to change notification settings - Fork 5
Fix --clone flag not working when starting workspace #34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: The call to
await runInit()in the container entrypoint lacks error handling, which can cause an infinite container restart loop on initialization failure, preventing SSH access.Severity: CRITICAL | Confidence: High
🔍 Detailed Analysis
The
runEntrypointfunction callsawait runInit()without atry...catchblock. IfrunInit()throws an error, for instance due to a failed git clone or a failing bootstrap script, the exception is not caught locally. This causes the entire container process to exit. Because the container is configured with arestartPolicy: 'unless-stopped', Docker will immediately restart it, leading to an infinite loop of startup, failure, and restart. The SSH daemon is started afterrunInit(), so this failure loop prevents it from ever running, making the workspace inaccessible for debugging.💡 Suggested Fix
Wrap the
await runInit()call within atry...catchblock. In the catch block, log the initialization error but do not exit the process. This will allow the container to finish starting up and enable the SSH daemon, letting users connect to the workspace to diagnose the problem.🤖 Prompt for AI Agent
Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID:
8299098