Fix exec examples: specify -u developer since container starts as root

DOCKER_HUB.md

@@ -46,10 +46,10 @@ docker run -d --name devbox \
   joakimp/opencode-devbox:latest sleep infinity
 
 # Shell 1: run opencode
-docker exec -it devbox opencode
+docker exec -it -u developer devbox opencode
 
 # Shell 2 (separate terminal): aws, git, etc.
-docker exec -it devbox bash
+docker exec -it -u developer devbox bash
 
 # When done
 docker rm -f devbox
@@ -59,8 +59,8 @@ With docker-compose this is simpler:
 
 ```bash
 docker compose up -d
-docker compose exec devbox opencode     # terminal 1
-docker compose exec devbox bash         # terminal 2
+docker compose exec -u developer devbox opencode     # terminal 1
+docker compose exec -u developer devbox bash         # terminal 2
 ```
 
 ## Environment Variables

README.md

@@ -76,10 +76,10 @@ docker compose run --rm devbox
 docker compose up -d
 
 # Attach a shell to the running container
-docker compose exec devbox bash
+docker compose exec -u developer devbox bash
 
 # Or run a single command inside it
-docker compose exec devbox aws --version
+docker compose exec -u developer devbox aws --version
 ```
 
 > `run` creates a new container (cleaned up with `--rm`). `exec` attaches to an already running one.

docker-compose.yml

@@ -3,7 +3,7 @@
 # Usage:
 #   cp .env.example .env    # configure your provider and keys
 #   docker compose up -d
-#   docker compose exec devbox opencode
+#   docker compose exec -u developer devbox opencode
 #
 # Or for interactive one-shot:
 #   docker compose run --rm devbox