🐳 Neko is a self hosted virtual browser that runs in docker and uses WebRTC.
🕹 f3l1x.io | 💻 f3l1x | 🐦 @xf3l1x
Forked version supporting Chrome DevTools Protocol.
- Create
docker-compose.ymlfile.
Copy docker-compose.yml file.
- Start Docker services.
docker compose up
- Open
http://localhost:8080in your browser. Loginneko/admin.
-
Use Chrome DevTools Protocol on
http://localhost:19222. -
Use Playwright MCP on
http://localhost:8931. -
Profit.
Tags on Docker Hub:
chromium- the latest buildchromium-YYYY.MM.DD- the build released on that date (for examplechromium-2026.11.09)
There is no latest tag. Every build is published as a GitHub release named after its date.
The image is built from holyfork/m1k1o-neko commit 7704fcc41399506fe91274b14e6473e100a949e9, pinned by NEKO_REF in VERSION. The fork is based on upstream n.eko master after v3.2.0 (Debian 13 images), plus 9 fork commits (Chrome DevTools Protocol, chrome-mcp and playwright-mcp).
To run a fixed build, set the image in your environment:
DOCKER_CHROMIUM_IMAGE=dockette/neko:chromium-2026.11.09 docker compose upCI clones the pinned fork commit, builds the image for linux/amd64, smoke tests it and, on master, pushes both tags and creates the release.
make test # validate docker-compose.yml
make build-chromium # fetch the pinned NEKO_REF and build the image (slow)
make test-docker # check that Chromium runs in the image
make run # start the stack
make version # print VERSION
make release # set VERSION to today (UTC)To update Neko, put a new full commit sha into NEKO_REF in VERSION and run make release.
See how to contribute to this package. Consider to support f3l1x. Thank you for using this package.
