-
Notifications
You must be signed in to change notification settings - Fork 695
Open
Description
Greetings,
I am not sure is it a bug, missed requirement, or desired behavior.
Problem statement
log.io in Docker container does not work OOTB.
You need additional configuration to be applied to make it work.
Therefore you need a strong knowledge of how a port listening and network interfaces binding work.
Actual behavior
/ # nc -zv logio 6689
/ # curl http://logio:6688
curl: (7) Failed to connect to logio port 6688: Connection refused
Additional inconvenience
Debug mode is turned on by default. It does spawning all processed logs entries in the output pipe.
Root cause
Bounding to the loopback interface (127.0.0.1) only. So connections from other network interfaces are not listened to.
Solution
- Changing the default configuration. PR will be provided.
- Adding an additional section in the documentation on how to use log.io in Docker or remote environments.
Metadata
Metadata
Assignees
Labels
No labels