Host state requires a deploy account that can write /var/lib/onebox

Aperta

#207 aperta il 23/9/2026 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà: 3/5
Tempo stimato: 1-2 giorni
Idoneità per principianti: 65/100

Tipo di issue: Bug
Chiarezza: Specificata chiaramente
Stato di attività: Attiva
Stack tecnologico: docker, go, shell
Ambito: cli, devops, infrastructure

Direzione di ricerca

Look at the host lock acquisition code, likely in a file like internal/host/lock.go or similar. The acquireHostLock function attempts to create /var/lib/onebox/_host. Examine the preflight check that reports this issue. The fix involves modifying the host state directory logic, possibly adding a host-level configuration or improving the error message and documentation. Test by setting up a non-root deploy account and running the bootstrap command.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

Problem

Since #206, host state (owner record, host lock, host journal, proxy) always lives at /var/lib/onebox/_host, whatever basePath says. That is what keeps a host to one application, but it means a deploy account that owns its basePath and cannot write /var/lib can no longer bootstrap: acquireHostLock fails on mkdir -p /var/lib/onebox/_host.

Before #206, _host sat under basePath, so a non-root account with basePath: /home/deploy/onebox worked.

Preflight now reports it (host state check), but no project setting fixes it. The only override, ONEBOX_TEST_HOST_STATE_DIR, is test-only by design.

Options

Document that the deploy account must be able to create /var/lib/onebox/_host, and have ob bootstrap say how to pre-create it with the right owner.
Or add a host-level (not project-level) setting for the host state directory, so it cannot differ per application on one host.

Lingua principale: Go
Stelle: 3
Fork: 0
Merge medio: 2h 44m
PR unite (30g): 49

Guida per i contributori

Apri la guida per i contributori

Come iniziare

Leggi tutta la issue e poi la guida ai contributi del progetto.
Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
Fai un fork del repository e lavora su un branch.
Apri una pull request che faccia riferimento al numero della issue.