docker: set up the data directory in an entrypoint (closes #166) #167

Merged

clawbot merged 1 commits from issue-166-entrypoint-data-dir into next

2026-10-01 21:15:03 +02:00

Author	SHA1	Message	Date
clawbot	e4ea3cd6a2	docker: set up the data directory in an entrypoint (closes #166 ) check / check (push) Successful in 1m16s Details The runtime image no longer sets USER. Its new entrypoint, deploy/docker-entrypoint.sh, runs as root: it creates the data directory if needed, gives it and everything in it to the dnswatcher user (uid 10001) with mode 700 on the directory, then runs dnswatcher as that user with su-exec. A bind-mounted host directory, whether empty and root-owned or holding a state file left by another uid, no longer has to be chowned first, and the README's upaas section now says only which path to mount. The startup check that the data directory is writable stays. Model: opus-5-5	2026-10-01 19:11:37 +00:00

Author

SHA1

Message

Date

clawbot

e4ea3cd6a2

docker: set up the data directory in an entrypoint (closes #166 )

check / check (push) Successful in 1m16s

Details

The runtime image no longer sets USER. Its new entrypoint,
deploy/docker-entrypoint.sh, runs as root: it creates the data
directory if needed, gives it and everything in it to the dnswatcher
user (uid 10001) with mode 700 on the directory, then runs dnswatcher
as that user with su-exec. A bind-mounted host directory, whether
empty and root-owned or holding a state file left by another uid, no
longer has to be chowned first, and the README's upaas section now says
only which path to mount. The startup check that the data directory is
writable stays.

Model: opus-5-5

2026-10-01 19:11:37 +00:00