Docker is telling you that the command hit an error. It is trying to run the node image with the command -w. Since -w is not a command, it throws this error. This is because you have written node in a place you probably didn't mean to. Your command is being interpreted like this: docker run -p portinfo -v volumeinfo node command You can rewrite your command like so and it should work fine: docker run -p 8085:3000 -v /home/joel/workspace/pluraldockerwebdev:/var/www -w '/var/www' node npm start. The first node is the image name and the second one is the command that docker will run which is node npm start; My issue was with the volume mounting, node wasn't able to find the package.json file since it was up a directory more so I just ran my same command but just add /Expresswebsite/ to give full path to package.json and it works now thanks again so the new command would be: docker run -p 8085:3000 -v /home/joel/workspace/pluraldockerwebdev/Expresswebsite/:/var/www -w '/var/www npm start Notice the volume mounting now includes /Expresswebsite to point to package.json. Thanks Ryan – Dec 14 '17 at 16:45.

There could be a few reasons for this - What you have there looks like log entries from /var/log/apache2/laravel4.162.243.55.229.xip.io-error.log, correct? (You're already a step ahead going to the logs:D ) This sounds like PHP5-FPM might not be listening on 127.0.0.1 or is not accepting connections from localhost. I would check:. Run sudo service apache2 configtest and see if there are any errors. Ensure php5-fpm is configured OK and running:. sudo service php5-fpm configtest. sudo service php5-fpm status Ensure that /etc/php5/fpm/pool.d/www.conf has the listen set to 127.0.0.1:9000, which Apache is attempting to send PHP requests to (it could still be set to the default /var/run/php5-fpm.sock file).

Erro Error Waiting For Container: Eof Issue 2789 Dockers

Ensure that /etc/php5/fpm/pool.d/www.conf isn't restricting localhost connections (127.0.0.1) via the;listen.allowedclients = 127.0.0.1 directive - keep that commented out, or set it to 127.0.0.1. Be sure to restart/reload apache/php5-fpm after any changes to their config files! Let me know what you see, hope this helps. Could be a bunch of things. In general, I would try:. sudo tail -n 50 -f /var/log/php5-fpm.log (see last 50 lines instead of the default, the error might be up higher). Tail the php5-fpm log in one session and restart php5-fpm in another, so you can see what gets spit out to the log while you start/restart FPM.

Erro Error Waiting For Container: Eof Issue 2789 Dockery

ps aux grep php to check if existing running php5-fpm processes still exist (zombie processes). Kill them kill -9 process-id-here if they exist (php5-fpm ones specifically). If php5-fpm is truly stopped and no processes are showing, try starting the process yourself manually and seeing if it outputs anything useful /usr/sbin/php5-fpm -nodaemonize -fpm-config /etc/php5/fpm/php-fpm.conf. Thanks for your help! Yes it worked out, what happened was i don't have a user called 'vagrant' on digital ocean. I think I'll create the user and in the future deployments just use that.

However, it would be nice in to have this a variable so there is some flexibility for deployment. Instead of it hardcoded to vagrant to have something else and pass it as a variable in the script and set it in the Vagrantfile. BTW, the reason why I am steering to digitalocean rather than AWS, is because it is significantly cheaper. Thanks again for your world class support!