I managed to get past this error by adjusting the owner/group of the config.exs file. On my local machine I did chmod -R 100:100 *
to get everything in the environments and volumes directories. (I discovered this by overriding the entrypoint so I could look at the filesystem before it rebooted. The userid of pleroma on my local machine did not match what the container had, so as a quick-and-dirty hack I put my local files to be 100:100 which seemed to be enough to get past the strict permissions check.)
HOWEVER... now it fails with:
pleroma | pleroma-db:5432 - accepting connections
pleroma | -- Running migrations...
pleroma | ** (EXIT from #PID<0.94.0>) shutdown
I got into the running container and tried manually running ./pleroma_ctl migrate
and it gave the same output.
I'm curious what's causing this, but it is also too nice outside for me to be spending any more time on this today.