Nginx-image has file system issues

[WouterrV]

Description:

When running docker-compose up nginx mysql workspace nginx exits with exit code 1. When running just docker-compose up nginx I get this:

λ docker-compose up nginx
laradock_php_docker-in-docker_1 is up-to-date
laradock_php_workspace_1 is up-to-date
laradock_php_php-fpm_1 is up-to-date
Starting laradock_php_nginx_1 ... done
Attaching to laradock_php_nginx_1
nginx_1                | Generating RSA private key, 2048 bit long modulus (2 primes)
nginx_1                | .....................................+++++
nginx_1                | ..............................+++++
nginx_1                | e is 65537 (0x010001)
nginx_1                | Signature ok
nginx_1                | subject=CN = default, O = default, C = UK
nginx_1                | Can't open /etc/nginx/ssl/default.crt for writing, No such file or directory
nginx_1                | 140208326905160:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/nginx/ssl/default.crt','w')
nginx_1                | 140208326905160:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:
nginx_1                | nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (17: File exists)
nginx_1                | 2020/04/27 14:32:59 [emerg] 11#11: open() "/var/log/nginx/error.log" failed (17: File exists)
laradock_php_nginx_1 exited with code 1

It seems that there's something wrong with the volume attached to nginx. How do I debug this? I think this happened after renaming my project directory but I'm not sure.

Context information:

Output of git rev-parse HEAD:3f71fc2c15216d61911b94c886f094e42e5efb57

Docker version is 19.03.8, docker-compose is 1.25.4. I'm running Windows 10 using Docker Desktop 2.2.0.5.

[m-elewa]

@WouterrV Try to update NGINX_SSL_PATH value in the .env file to match the new nginx ssl location on the host machine

[stale]

Hi 👋 this issue has been automatically marked as stale 📌 because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions ❤️.

[stale]

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.