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

Why is the service listening address not 0.0.0.0 but 127.0.0.1 #81

Closed
Ethan-devops opened this issue Jul 31, 2023 · 2 comments · Fixed by #83
Closed

Why is the service listening address not 0.0.0.0 but 127.0.0.1 #81

Ethan-devops opened this issue Jul 31, 2023 · 2 comments · Fixed by #83

Comments

@Ethan-devops
Copy link

Why is the service listening address not 0.0.0.0 but 127.0.0.1

Please change the listener to 0.0.0.0 so that the remote server can be supported, and the -p option can be supported when running in container mode

@Lyt99
Copy link
Collaborator

Lyt99 commented Jul 31, 2023

Hi, thanks for your issue!

We've used 127.0.0.1:8080 as default for security reason. This behavior for now can be changed with --http-address. For example, --http-address :8080 sets the address of HTTP UI to 0.0.0.0:8080.

It seems that the documentation provides a wrong way to run skoop in docker container. I will try to fix it today, with documentation or default value changed.

@Ethan-devops
Copy link
Author

Yes, you're right, the documentation provides a faulty way to run Skoop in a Docker container.

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

Successfully merging a pull request may close this issue.

2 participants