danilomendonca opened a new issue #3123: Nginx container fails to start URL: https://github.com/apache/incubator-openwhisk/issues/3123 I'm having a problem with the local environment created with Vagrant. The first time the box is started, Nginx container starts correctly. From the second time on, it fails to start with the message: 2017/12/20 09:25:13 [emerg] 1#1: open() "/etc/nginx/nginx.conf" failed (2: No such file or directory) nginx: [emerg] open() "/etc/nginx/nginx.conf" failed (2: No such file or directory) I've noticed the files inside /tmp/wskconf and /tmp/wsklogs are not elsewhere in the VM. I am not familiar with how Docker containers are configured and started, but I wonder if the first time the VM is started the files inside /tmp are been used. If that's the case, they are obviously gone by the time the VM is restarted. ## Environment details: * local deployment, Ubuntu 14.04 (Host) with Vagrant 1.8.1, Ubuntu 14.04 (installed by hello) ## Steps to reproduce the issue: 1. Execute tools/vagrant/hello to create the Vagrant box 2. Halt the VM and restart it 3. Nginx container fails to start ## Provide the expected results and outputs: Expected to be able to halt and start the vagrant box, i.e., that openwhisk would be fully functional without further configurations. ## Provide the actual results and outputs: From the second time on, nginx container fails to start with the following message: 2017/12/20 09:25:13 [emerg] 1#1: open() "/etc/nginx/nginx.conf" failed (2: No such file or directory) nginx: [emerg] open() "/etc/nginx/nginx.conf" failed (2: No such file or directory) ## Additional information you deem important: From the output, the deployment script is successfully executed. Openwhisk is fully functional until the VM is restarted.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
