Repository navigation
Conversation
Run Pi Pocket in a container from a thin Node image with Chromium, git, gh, ripgrep, fd, and cloudflared. The database, extensions, themes, Pi's folder, and the workspace are bind-mounted from the host, so they survive rebuilds. - docker/Dockerfile, entrypoint that clears stale Chromium profile locks - docker-compose.yml with LAN defaults and healthcheck - .env.example for ports, access mode, folders, and optional provider keys - docs/docker.md, linked from the README and docs index - .gitignore, .prettierignore, and eslint ignore the compose ./data folder
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
Runs Pi Pocket in a container, with the same setup for Docker and Podman.
docker/Dockerfile: thinnode:24-bookworm-slimimage. Installs the runtime packages plus Chromium (Browser panel),git,gh,ripgrep,fd, andcloudflared. Runs the app from source like the launcher does.docker/entrypoint.sh: clears Chromium's staleSingleton*profile locks before start, so a recreated container can use the bind-mounted profile.docker-compose.yml: publishes the port, sets LAN defaults, and bind-mounts the database, extensions, themes, Pi's folder, and the workspace from the host. Includes a healthcheck..env.example: ports, bind address, access mode, host folders, optional provider keys.docs/docker.md, linked fromREADME.mdanddocs/index.md: folders, permissions, access modes, and updates..gitignore,.prettierignore,eslint.config.js: ignore the compose./datafolder.Why
The launcher assumes an interactive terminal. A container gives a headless, restartable server whose state lives on the host, so rebuilds and updates do not lose sign-ins, extensions, or work.
Tested
npx prettier --checkon the Markdown/YAML/JS files (ignore/env/Dockerfile/shell have no parser).npx eslint eslint.config.js.npm run checkandnpm testare unaffected.The remaining working-tree changes (
registerModelProviderinsrc/server/*,types/pocket.d.ts, and its reference docs) are a separate feature and are not part of this PR.