amazon web services - AWS EB, Play Framework and Docker: Application Already running -
i running play 2.2.3 web application on aws elastic beanstalk, using sbts ability generate docker images. uploading image eb administration interface works, gets state consistently following error:
docker container quit unexpectedly on thu nov 27 10:05:37 utc 2014: play server process id 1 application running (or delete /opt/docker/running_pid file).
and deployment fails. cannot out of doing else terminating environment , setting again. how can avoid environment gets state?
sounds may running infamous pid 1 issue. docker uses new pid namespace each container, means first process gets pid 1. pid 1 special id should used processes designed use it. try using supervisord instead of having playframework running primary processes , see if resolves issue? hopefully, supervisord handles amazon's termination commands better play framework.
Comments
Post a Comment