Thanks for reporting!
The last alpha build moved
ENV PS_IS_DOCKER=1
from the Dockerfile to the docker-entrypoint.sh because some docker container managers were exposing the ENV to the user, and I thought that would be equivalent.
Spoiler alert:
it isn’t. If you shell into the container, the docker-entrypoint.sh isn’t run:
$ docker exec -u photostructure -it 48dcf33ed4d3 bash
node@48dcf33ed4d3:/opt/photostructure$ env | grep DOCKER
So PhotoStructure thinks it’s on a normal server running Debian.
What is
/tmp/.photostructure-cache-1032/logs/**/*.log?
It’s the default log directory on non-docker linux, if there isn’t a ~/.config dir.
I originally implemented one of the tests in this horrible set of heuristics, and finally threw up my hands and went with the explicit env approach, but I think checking /proc/1/comm for tini should should be simple enough and more reliable.
Until I get out a fix, be sure to run export PS_IS_DOCKER=1 after shelling into your PhotoStructure docker container, and things should work properly.
I’ll get this fix out today.