Closed charlyoleg closed 3 years ago
Hi, this error doesn't look familiar. How is the resource usage on your server? Is it possible the container would be killed by your OS because of a lack of available memory?
After getting the error on my OVH VPS, I have tried the docker-compose.yaml on my personal laptop, that has plenty of resources (16GB RAM) and I got exactly the same error. By googling, I saw similar error related to Redis containers. Unfortunately, I'm not familiar with Redis configuration and setup.
I'm successfully reproducing this on a clean install…
So I think I found the culprit: in fact, the crash was higher in the stack trace, with an ownership issue on the postgres directory. I suspect the postgres processed crashed, thus causing the redis server to be killed by s6.
Would you mind trying again with the funkwhale/all-in-one:develop
tag?
Thank you! The restarting issue is fixed. I will proceed further with the installation.
Describe the bug Following the instructions for mono-container installation on my OVH-VPS server, after the command 'docker-compose up -d', I see my funkwhale container starting and then stopping and then restarting in an endless loop. According to the log, the container received 'Received SIGTERM scheduling shutdown...'. I don't know what emit this SIGTERM: OVH? Some internal error?
Logs
Options Submit your command options and arguments like volumes, environment variables, and ports.
System information
docker-compose version 1.17.1, build unknown
Additional context This happens on an OVH VPS server and also on my Ubuntu laptop.