farhoodlabs/devcontainer
8
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 39 Wiki Activity

fix: make Chrome work inside Docker for Claude Max OAuth login #14

Merged
cpfarhood merged 1 commits from fix/chrome-in-docker into main 2026-02-20 14:31:59 +00:00
Conversation 0 Commits 1 Files Changed 1
+10 -3
cpfarhood commented 2026-02-20 14:30:52 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Summary

  • Chrome crashes silently inside Docker without --no-sandbox and --disable-dev-shm-usage, so the OAuth browser popup never completes
  • Creates a /usr/local/bin/google-chrome wrapper that injects these required container flags
  • Sets BROWSER=/usr/local/bin/google-chrome so Claude Code (which calls xdg-open on Linux) and any other tool uses the wrapper automatically
  • Adds xdg-utils to ensure xdg-open can resolve browser handlers in the VNC environment

The OAuth callback flow works correctly once Chrome actually runs — both the browser and Claude Code's local auth server are in the same container network namespace, so the localhost redirect completes normally.

Test plan

  • Build and deploy the updated image
  • Open a terminal in the VNC session
  • Run claude — it should open Chrome in the VNC window pointing to the Claude login page
  • Log in with a Claude Max account — OAuth should complete and claude should show as authenticated
  • Start Happy Coder — confirm it connects without complaining about auth

🤖 Generated with Claude Code

## Summary - Chrome crashes silently inside Docker without `--no-sandbox` and `--disable-dev-shm-usage`, so the OAuth browser popup never completes - Creates a `/usr/local/bin/google-chrome` wrapper that injects these required container flags - Sets `BROWSER=/usr/local/bin/google-chrome` so Claude Code (which calls `xdg-open` on Linux) and any other tool uses the wrapper automatically - Adds `xdg-utils` to ensure `xdg-open` can resolve browser handlers in the VNC environment The OAuth callback flow works correctly once Chrome actually runs — both the browser and Claude Code's local auth server are in the same container network namespace, so the `localhost` redirect completes normally. ## Test plan - [ ] Build and deploy the updated image - [ ] Open a terminal in the VNC session - [ ] Run `claude` — it should open Chrome in the VNC window pointing to the Claude login page - [ ] Log in with a Claude Max account — OAuth should complete and `claude` should show as authenticated - [ ] Start Happy Coder — confirm it connects without complaining about auth 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
antigravity
architecture
automation
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 examples
good first issue
Good for newcomers
 helm
help wanted
Extra attention is needed
 invalid
This doesn't seem right
 maintainability
monitoring
question
Further information is requested
 refactor
tooling
user-experience
validation
wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
fl_blake (Blake MIddleware) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) flux (Flux CD) admin (Gitea Admin) fl_hugh (Hugh Commit) renovate (Mend Renovate) fl_warren (Warren Bufferpool)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: farhoodlabs/devcontainer#14
Delete Branch "fix/chrome-in-docker"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?