fix(docker): fix data volume ownership on fresh bind mounts

/app/data is a bind mount, so the chown baked into the image is
overwritten by the host directory's ownership at runtime. On a fresh
prod deploy Docker creates ./data as root-owned, but the container ran
as the non-root nextjs user, so Prisma couldn't open lovelope.db
("unable to open database file").

Add an entrypoint that starts as root, chowns /app/data, then drops to
nextjs via su-exec before running migrations and starting the server.

This commit is contained in:

Paul Goncalves Monnet

2026-07-30 16:40:45 +02:00

parent cd36fc5723

commit 75ea9b7416

2 changed files with 10 additions and 4 deletions

									
										docker-entrypoint.sh
									
		+6
		
												View File
												
				@@ -0,0 +1,6 @@

				#!/bin/sh

				set -e

				chown -R nextjs:nodejs /app/data

				exec su-exec nextjs sh -c "npx prisma migrate deploy && node server.js"