This is on an Ubuntu 14.04 LTS VM running Docker and I suspect
respawn is the cause of my problem but not sure of the ideal solution.
Current upstart script (
description "Start docker containers" author "Batman" start on filesystem and started docker stop on runlevel [!2345] respawn script docker-compose -f /usr/bin/myapp/docker-compose.yml -p myapp start end script
This 'works' in that
myapp is alive and responsive but
/sbin/init takes up all the CPU when I monitor with
htop. If I remove the entry from upstart (
sudo rm /etc/init/dockersuitecrm.conf) and manually SSH in and run
docker-compose -f /usr/bin/myapp/docker-compose.yml -p myapp start I don't see the cpu at 100% issue and as before
myapp is again alive and responsive.
So I suspect the way I'm starting docker-compose above is incorrect. What's the right way to start
docker-compose is always running without manual intervention?
EDIT: Shouldn't matter but
/usr/bin/myapp -> /home/batman/dockerapps/myapp as a symbolic link.