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.

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

Using debugging mode inside a container is impossible because the console host is not parametrized #591

Open
heolin opened this issue Dec 19, 2023 · 0 comments

Comments

@heolin
Copy link

heolin commented Dec 19, 2023

Version: v0.10.21

Using debugging mode inside a container is impossible because the console host is not parametrized. Faust CLI allows specifying aiomonitor console port using the --console-port parameter. Unfortunately, since "console-host" is not available, it's using the default host address specified in aiomonitor, which is 127.0.0.1.
This problem affects both configurations that are using docker containers and Kubernetes setup. Changing it manually in aiomonitor source code to 0.0.0.0 solved the issue both in Docker and Kubernetes.

Steps to reproduce

  • Run a Faust worker from within a docker container with the --debug parameter enabled.
  • In the console output, you will see a Starting console at 127.0.0.1:50101 message instead of localhost.
  • Accessing the debugging console from outside the container is impossible.

Expected behavior

Actual behavior

  • aiomonitor console is running on the default host address: 127.0.0.1.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant