Migrations/neko
1
0
Fork 0
mirror of https://github.com/m1k1o/neko.git synced 2026-11-03 08:21:50 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: add Brave singleton lock fix to troubleshooting (closes #609) (#663)

Browse Source
This commit is contained in:
Miroslav Šedivý
2026-07-31 11:34:20 +02:00
committed by GitHub
parent b1a4055228
commit 2f9c20bb97
1 changed files with 49 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
webpage/docs/troubleshooting.md
+49
View File
@@ -260,6 +260,55 @@ docker exec -it <container-id> ls -la /home/neko/.config/google-chrome
docker exec -it <container-id> chown -R neko:neko /home/neko/.config/google-chrome docker exec -it <container-id> chown -R neko:neko /home/neko/.config/google-chrome
``` ```
#### Brave browser: singleton lock files preventing startup {#brave-singleton-lock}
Brave (and other Chromium-based browsers) write singleton lock files (`SingletonLock`, `SingletonCookie`, `SingletonSocket`) to the profile directory when they start. If the container is stopped uncleanly, these files are left behind and the next container start fails because Brave thinks another instance is already running.
**Fix 1: Remove lock files on container startup**
Override the container's `command` to delete the stale lock files before launching supervisord:
```yaml title="docker-compose.yaml"
services:
neko:
image: "ghcr.io/m1k1o/neko/brave:latest"
restart: "unless-stopped"
shm_size: "2gb"
ports:
- "8080:8080"
- "52000-52100:52000-52100/udp"
volumes:
- /data:/home/neko/.config/brave
environment:
NEKO_DESKTOP_SCREEN: 1920x1080@30
NEKO_MEMBER_MULTIUSER_USER_PASSWORD: neko
NEKO_MEMBER_MULTIUSER_ADMIN_PASSWORD: admin
NEKO_WEBRTC_EPR: 52000-52100
# highlight-start
command: >
sh -c "rm -f /home/neko/.config/brave/SingletonLock
/home/neko/.config/brave/SingletonCookie
/home/neko/.config/brave/SingletonSocket &&
exec /usr/bin/supervisord -c /etc/neko/supervisord.conf"
# highlight-end
```
**Fix 2: Set a persistent container hostname**
Chromium-based browsers also embed the hostname in the singleton lock. If the container hostname changes on every restart (which is Docker's default), the browser may refuse to reuse the profile. Setting a fixed hostname avoids this:
```yaml title="docker-compose.yaml"
services:
neko:
image: "ghcr.io/m1k1o/neko/brave:latest"
# highlight-start
hostname: neko
# highlight-end
volumes:
- /data:/home/neko/.config/brave
# ...
```
### Common server errors {#common-server-errors} ### Common server errors {#common-server-errors}
``` ```