Guoguo 5e44a99410 fix(docker): run self-built images as root for parity with release (#2435) ... The self-built docker/Dockerfile and docker/Dockerfile.heavy created a dedicated picoclaw user (uid 1000) and stored config at /home/picoclaw/.picoclaw, while the released images from Dockerfile.goreleaser (and Dockerfile.full) run as root at /root/.picoclaw. Both docker-compose files mount ./data:/root/.picoclaw, so self-built images silently broke when used with the shared compose. Drop the picoclaw user switch and align both Dockerfiles on root + /root/.picoclaw. Dockerfile also adopts the release entrypoint.sh so first-run behavior matches between self-built and release tags. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-04-09 10:53:52 +08:00
..
docker-compose.full.yml	fix: address PR review feedback for MCP tools support	2026-03-01 10:56:02 +08:00
docker-compose.yml	fix(docker): add -console flag and open network for launcher (#2314)	2026-04-07 09:34:54 +08:00
Dockerfile	fix(docker): run self-built images as root for parity with release (#2435)	2026-04-09 10:53:52 +08:00
Dockerfile.full	fix: address PR review feedback for MCP tools support	2026-03-01 10:56:02 +08:00
Dockerfile.goreleaser	chore(docker): reorganize docker files and add first-run entrypoint (#812)	2026-02-27 10:10:17 +08:00
Dockerfile.goreleaser.launcher	fix(docker): add -console flag and open network for launcher (#2314)	2026-04-07 09:34:54 +08:00
Dockerfile.heavy	fix(docker): run self-built images as root for parity with release (#2435)	2026-04-09 10:53:52 +08:00
entrypoint.sh	chore(docker): reorganize docker files and add first-run entrypoint (#812)	2026-02-27 10:10:17 +08:00