[GH-ISSUE #247] Default configuration does not work in Docker #199

New issue

Open

opened 2026-02-26 05:31:35 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 05:31:35 +03:00

Owner

Originally created by @sprymiker on GitHub (Aug 1, 2020).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/247

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.

Originally created by @sprymiker on GitHub (Aug 1, 2020). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/247 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 1. Changing the default configuration. PR will be provided. 2. Adding an additional section in the documentation on how to use log.io in Docker or remote environments.

kerem commented

2026-02-26 05:31:35 +03:00

Author

Owner

@sprymiker commented on GitHub (Aug 1, 2020):

The PR: https://github.com/NarrativeScience/log.io/pull/248

@sprymiker commented on GitHub (Aug 1, 2020): The PR: https://github.com/NarrativeScience/log.io/pull/248