-
Notifications
You must be signed in to change notification settings - Fork 19
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
0.0.0.0:80: bind: address already in use, errors in logs #24
Comments
hi @biguphpc thank you for opening this issue! @smusali and I are looking into this and will get back to you. Does this issue also surface if you use one of our other available Docker setup methods? For example:
Also do you have any other processes running on port 80? You can run lsof -i:80 to check and send a kill -9 with the associated pid (https://stackoverflow.com/questions/3855127/find-and-kill-process-locking-port-3000-on-mac) |
Yes we do have other processes running on port 80 and do not want to kill our web server running on port 80. |
I understand @biguphpc. So it looks like official logspout listens on port 80 by default (https://github.com/gliderlabs/logspout) and it can be configured via the PORT variable (see the environment variable section of the logspout README). Would update the environment section in your docker compose file to contain the desired port. Environment variables (section in the official logspout README): Sample docker compose file using the PORT environment variable:
|
@biguphpc following up- did that help resolve your issue? |
Hi, we've having constant errors in the logs when starting this container.
This seems to happen every minute. Here's the
docker-compose.yaml
we're using:Thanks
The text was updated successfully, but these errors were encountered: