justinmclean opened a new issue, #4209:
URL: https://github.com/apache/iggy/issues/4209

   ### Description
   
   `docker run -p 8090:8090 apache/iggy` starts cleanly, but the host can't 
connect to it.
   
   The published image (`core/server/Dockerfile`) sets no listener addresses, 
so the server listens on the `127.0.0.1` defaults from `config.toml`. Nothing 
in the log says so. The startup check in `validate_client_facing_address` 
(`core/configs/src/server_config/validators.rs`) only covers wildcard 
addresses, not loopback.
   
   On first start with no root credentials set, the server logs a generated 
root password once. If that's missed, the only way to recover is to delete the 
data directory. Only the README says so.
   
   ### Affected area / component
   
   Iggy server, Configuration
   
   ### Proposed solution
   
   - When the server runs in a container and the client-facing listener is on a 
loopback address, log a warning. Name the setting to change, for example 
`IGGY_TCP_ADDRESS=0.0.0.0:8090` together with `IGGY_NODE_ADVERTISED_ADDRESS`. 
It should be a warning, not an error, since loopback-only is sometimes 
intended. Outside a container, loopback is the normal default and needs no 
warning.
   - Add the recovery step to the generated password message in 
`core/server/src/boot/credentials.rs`, for example "This is shown once. To 
reset it, delete the data directory."
   
   ### Alternatives considered
   
   Set the listener addresses in the published image, as the repository's own 
`Dockerfile` does. That also needs `IGGY_NODE_ADVERTISED_ADDRESS`, which the 
image can't know, so the server would refuse to start instead.
   
   ### Contribution
   
   - [ ] I'm willing to submit a pull request to implement this feature
   
   ### Good first issue
   
   - [ ] I think this could be a good first issue for a new contributor
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to