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.

Sign up for GitHub

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

Jump to bottom

Apache logs from the civicrm container do not propogate to the host #12

Closed
michaelmcandrew opened this issue Mar 2, 2018 · 2 comments
Closed

Apache logs from the civicrm container do not propogate to the host #12

michaelmcandrew opened this issue Mar 2, 2018 · 2 comments

Comments

@michaelmcandrew
Copy link
Owner

michaelmcandrew commented Mar 2, 2018 •
edited
Loading

amp defines a custom log file for apache that prevents Docker from handling the logs. See amp-cli/amp#52 for more details.

As soon as civicrm/civicrm-buildkit#396 is merged, we can create a new Docker image based on a newer version of buildkit that uses the custom vhost and config added in this commit: 65a0971.

Until then, a workaround is to manually edit the vhost files in /buildkit/.amp/apache.d and remove the lines that define the custom logs.
@michaelmcandrew michaelmcandrew changed the title Apache logs not visible in the container Apache logs from the civicrm container do not propogate to the host Mar 2, 2018
@totten
Copy link

totten commented Mar 6, 2018

The dependency civicrm/civicrm-buildkit#396 is now merged.

@michaelmcandrew
Copy link
Owner Author

thanks @totten - closing this issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@michaelmcandrew @totten