fix: remove sudo from happy daemon start — startapp.sh already runs as app user

sudo -u failed because the app user is not in sudoers. It was unnecessary anyway: startapp.sh (and init-repo.sh) run as the app user (UID 1000) so happy daemon start already executes as the correct user with the right HOME. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Merge pull request #15 from cpfarhood/fix/happy-daemon-user
2026-02-20 10:05:41 -05:00 · 2026-02-20 10:01:06 -05:00 · 2026-02-20 09:59:59 -05:00 · 2026-02-20 09:31:59 -05:00 · 2026-02-20 09:30:36 -05:00
2 changed files with 13 additions and 5 deletions
@@ -25,13 +25,19 @@ RUN apt-get update && apt-get install -y \
    sudo \
    && rm -rf /var/lib/apt/lists/*

-# Install Chrome
+# Install Chrome and xdg-utils (needed for xdg-open to work in VNC)
 RUN wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | gpg --dearmor -o /usr/share/keyrings/google-chrome-keyring.gpg && \
    echo "deb [arch=amd64 signed-by=/usr/share/keyrings/google-chrome-keyring.gpg] http://dl.google.com/linux/chrome/deb/ stable main" > /etc/apt/sources.list.d/google-chrome.list && \
    apt-get update && \
-    apt-get install -y google-chrome-stable && \
+    apt-get install -y google-chrome-stable xdg-utils && \
    rm -rf /var/lib/apt/lists/*

+# Chrome wrapper: adds flags required for running inside a Docker container.
+# xdg-open (used by Claude Code on Linux) respects $BROWSER, so pointing it
+# here ensures the OAuth popup works without manual --no-sandbox invocations.
+RUN printf '#!/bin/bash\nexec /usr/bin/google-chrome-stable \\\n  --no-sandbox \\\n  --disable-dev-shm-usage \\\n  --disable-gpu \\\n  "$@"\n' > /usr/local/bin/google-chrome && \
+    chmod +x /usr/local/bin/google-chrome
+
 # Install Node.js (LTS version for Happy Coder)
 RUN curl -fsSL https://deb.nodesource.com/setup_lts.x | bash - && \
    apt-get install -y nodejs && \
@@ -69,7 +75,8 @@ WORKDIR /workspace

 # Configure container to run as user user
 ENV HOME=/home/user \
-    USER=user
+    USER=user \
+    BROWSER=/usr/local/bin/google-chrome

 # Expose VNC port (baseimage-gui default)
 EXPOSE 5800
@@ -59,10 +59,11 @@ chown -R "$RUN_UID:$RUN_GID" "$WORKSPACE_DIR"
 mkdir -p "$HOME"
 chown "$RUN_UID:$RUN_GID" "$HOME"

-# Start Happy Coder daemon
+# Start Happy Coder daemon. startapp.sh already runs as the app user (UID 1000),
+# so no sudo needed — Happy/Claude Code will find credentials in the correct home dir.
 echo "Starting Happy Coder..."
-cd "$WORKSPACE_DIR"

+cd "$WORKSPACE_DIR"
 happy daemon start || echo "Happy Coder daemon failed to start, continuing anyway..."

 echo "Happy Coder daemon started"
Author	SHA1	Message	Date
Chris Farhood	e89c3040b7	fix: remove sudo from happy daemon start — startapp.sh already runs as app user sudo -u failed because the app user is not in sudoers. It was unnecessary anyway: startapp.sh (and init-repo.sh) run as the app user (UID 1000) so happy daemon start already executes as the correct user with the right HOME. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-02-20 10:05:41 -05:00
Chris Farhood	8d7b39f1b5	Merge pull request #15 from cpfarhood/fix/happy-daemon-user fix: run Happy daemon as app user so it can find credentials	2026-02-20 10:01:06 -05:00
Chris Farhood	32e87254d2	fix: run Happy daemon as app user, not root When init-repo.sh starts the happy daemon as root, HOME=/root so Happy and Claude Code can't find credentials stored in /home/user. The mobile app works when the user manually runs happy from a VSCode terminal (as the user user) because the right home dir is in scope. Use sudo -u with -E (preserve environment) so the daemon runs as the correct user while still inheriting the pod's env vars (HAPPY_SERVER_URL, HAPPY_WEBAPP_URL, ANTHROPIC_API_KEY, etc.). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-02-20 09:59:59 -05:00
Chris Farhood	66ccee1202	Merge pull request #14 from cpfarhood/fix/chrome-in-docker fix: make Chrome work inside Docker for Claude Max OAuth login	2026-02-20 09:31:59 -05:00
Chris Farhood	1909c2a3aa	fix: make Chrome work inside Docker for Claude OAuth browser login Chrome requires --no-sandbox and --disable-dev-shm-usage when running inside a Docker container, otherwise it crashes silently and the OAuth popup never completes. - Add a /usr/local/bin/google-chrome wrapper that injects these flags - Install xdg-utils so xdg-open can resolve browser handlers in VNC - Set BROWSER env var to the wrapper so Claude Code and xdg-open both use it when opening the Claude Max login URL The OAuth callback (to localhost) works fine inside VNC because both the browser and the Claude Code local auth server share the same container network namespace. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-02-20 09:30:36 -05:00