Create a missing volume host directory before starting an app container #235

New Issue

2026-09-29T11:09:18+02:00

clawbot commented

2026-09-29 11:09:18 +02:00

sneak ruled on 2026-09-29 that an app's operator never pre-creates or chowns a host directory for the app's data, and no README tells him to (filed for pixa as sneak/pixa#159). The container sets its data directory's permissions itself.

That covers ownership, but not existence. upaas mounts an app volume as a bind mount through Docker's mount API (buildMounts in internal/docker/client.go, mount.TypeBind), and Docker refuses a bind mount whose host path does not exist. upaas does not create the path first, so a new app's first deploy fails unless someone runs mkdir on the host, which the ruling rules out.

Definition of done

Before creating an app's container, upaas creates each of the app's volume host paths that does not exist yet (os.MkdirAll, mode 0755, owned by root; the container fixes ownership itself). An existing path is left alone.
A test covers a missing path being created and an existing one being left untouched.
README: the volume section says upaas creates a missing host directory, and nothing tells the operator to create one.

Model: opus-5-5

sneak ruled on 2026-09-29 that an app's operator never pre-creates or chowns a host directory for the app's data, and no README tells him to (filed for pixa as https://git.eeqj.de/sneak/pixa/issues/159). The container sets its data directory's permissions itself. That covers ownership, but not existence. upaas mounts an app volume as a bind mount through Docker's mount API (`buildMounts` in `internal/docker/client.go`, `mount.TypeBind`), and Docker refuses a bind mount whose host path does not exist. upaas does not create the path first, so a new app's first deploy fails unless someone runs `mkdir` on the host, which the ruling rules out. ## Definition of done - Before creating an app's container, upaas creates each of the app's volume host paths that does not exist yet (`os.MkdirAll`, mode 0755, owned by root; the container fixes ownership itself). An existing path is left alone. - A test covers a missing path being created and an existing one being left untouched. - README: the volume section says upaas creates a missing host directory, and nothing tells the operator to create one. Model: opus-5-5

clawbot referenced this issue from sneak/pixa

2026-09-29 11:09:26 +02:00

The container sets its data directory permissions itself before startup #159

clawbot referenced this issue from sneak/pixa

2026-09-29 11:35:20 +02:00

Container makes /var/lib/pixa usable before starting pixad #161

clawbot referenced this issue from sneak/webhooker

2026-09-29 11:49:34 +02:00

Container sets its data directory's owner and mode itself #353

clawbot referenced this issue from sneak/webhooker

2026-09-29 12:40:17 +02:00

After a restart under upaas: new admin password, and logging in with it returns 500 #359