When the `start-docker` script is executed, some process is not properly
cleaned up and ends up in a zombie state.
Using the `init` flag when launching the container runs an init process
inside the container that will forward signals to node and reap
processes.
Fixes: #1428
I'd like to propose to delete from docker-compose a redundant volume mapping. As I see that `sql` directory had been deleted and now umami-app is responsible for migration.
I'd like to propose a minor changes that can bring more stability in launching the umami server with docker-compose by adding a certain healthcheck for db container and a certain condition for depends_on directive for umami-app container
It might be a good idea to add a restart policy to the default `docker-compose.yml` file.
Either: `restart: always` or `restart: unless-stopped`
Useful in case Umami crashes for some reason (see #721)
This is also useful in case the server restarts, so Umami starts up again after rebooting.
https://docs.docker.com/config/containers/start-containers-automatically/
