Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apache2 fails to start #1174

Closed
jelovac opened this issue Oct 5, 2017 · 4 comments
Closed

apache2 fails to start #1174

jelovac opened this issue Oct 5, 2017 · 4 comments
Labels

Comments

@jelovac
Copy link

jelovac commented Oct 5, 2017

Info:

  • Docker version: 17.07.0-ce, build 8784753
  • Laradock commit: a2edf57
  • System info (Mac, PC, Linux): Windows 10
  • Additional info: Docker toolbox for Windows using Virtualbox as docker provider

Issue:

Apache virtual host .conf files are not copied to workspace container and because of that the apache2 service fails.

2017-10-05 16:36:22,836 INFO spawned: 'apached' with pid 1319
-> Executing /opt/docker/bin/service.d/httpd.d//10-init.sh
2017-10-05 16:36:22,881 INFO success: apached entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
apache2: Syntax error on line 219 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/sites-enabled/vhost.conf: No matches for the wildcard '*.conf' in '/etc/apache2/sites-available', failing (use IncludeOptional if required)
2017-10-05 16:36:22,977 INFO exited: apached (exit status 1; not expected)
2017-10-05 16:36:23,988 INFO spawned: 'apached' with pid 1324
-> Executing /opt/docker/bin/service.d/httpd.d//10-init.sh
2017-10-05 16:36:24,029 INFO success: apached entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
apache2: Syntax error on line 219 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/sites-enabled/vhost.conf: No matches for the wildcard '*.conf' in '/etc/apache2/sites-available', failing (use IncludeOptional if required)
2017-10-05 16:36:24,128 INFO exited: apached (exit status 1; not expected)

Expected behavior:

The .conf files should have been copied to the apache2 sites-available directory.


Reproduce:


Relevant Information:

The reason why it fails is because default.apache.conf has not been copied, I also tried to create additional *.conf files in the laradock/apache2/sites directory but for some reason they are not copied when I rebuild the containers.

@jelovac jelovac changed the title Apache2 fails to start apache2 fails to start Oct 5, 2017
@ChrGriffin
Copy link

Windows 7, Docker 17.07.0-ce. Encountering this same issue.

@devployment
Copy link

Just in case. If you changed your Windows password recently, make sure that the drives you need are shared in the Docker settings again. It just happened to me that these shares were lost. Probably as I had to change my password recently.

So I created a new DockerUser and gave it the needed (admin) rights. By this it should not happen anymore if the company policy forces me to change my password. Or just use your Windows user and make sure everything is shared as needed.

@stale
Copy link

stale bot commented Feb 2, 2020

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 stale bot added the Stale label Feb 2, 2020
@stale
Copy link

stale bot commented Feb 23, 2020

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 🎈.

@stale stale bot closed this as completed Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants