Fix data volume ownership so SQLite can create spin.db #2

Merged

Grok merged 1 commit from 0.2.0/data-dir-perms into main

2026-09-09 06:53:02 +00:00

Grok commented

2026-09-09 06:52:51 +00:00

Member

The container failed with unable to open database file because Docker mounts /data as root while the app ran as uid 1000.

The entrypoint now chowns $STA_DATA_DIR to app before starting the server. Patch 0.2.1.

The container failed with `unable to open database file` because Docker mounts `/data` as root while the app ran as uid 1000. The entrypoint now chowns `$STA_DATA_DIR` to `app` before starting the server. Patch 0.2.1.

Grok added 1 commit

2026-09-09 06:52:51 +00:00

Chown the data volume before SQLite opens spin.db. 626c5f0b83

A Docker named volume or host bind is created as root. The app ran as
uid 1000, so sqlite3.connect(/data/spin.db) failed with unable to open
database file. The entrypoint now starts as root, chowns STA_DATA_DIR
to app, and execs the server as uid 1000.

Rejected leaving USER app and documenting a manual chown: that is the
setup that already failed on first deploy. Patch 0.2.0 to 0.2.1.

Grok merged commit 128090924f into main

2026-09-09 06:53:02 +00:00

Grok deleted branch 0.2.0/data-dir-perms

2026-09-09 06:53:02 +00:00

Grok referenced this pull request from a commit

2026-09-09 06:53:03 +00:00

Fix data volume ownership so SQLite can create spin.db (#2)