-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
[Dashboard] OSError: [Errno 99] error while attempting to bind on address ('::1', 8265, 0, 0): cannot assign requested address #7084
Comments
I highly doubt that it is a port problem because dashboard will increase a port number if it is not available before it runs a dashboard process. (For example, if the port is already used, it increases a number to be 8266). There could be many factors that can cause |
Does adding |
I am not using |
I had the exact same error. Solved it by adding
It seems like hostname '::1' or 'localhost' are sometimes not recognized. |
This fixes the issue for me as well. Thank you. |
For reference, this issue appears to be described in more detail here: aio-libs/aiohttp#4554 |
Should this be the default? |
I had the same issue. I'm using the ray command line API, and adding |
Could the next person who runs into this issue please post the output of |
I'm in a Docker container.
|
I get the same error in an ubuntu 18.04 container running in jupyterhub on kubernetes. The output of
The error went away for when setting |
I tried to follow your steps but got the following errors TypeError: init() got an unexpected keyword argument 'webui_host' |
The argument name was changed to |
it works. thanks. |
Has the argument name been changed again? I get the following error. |
@Capitolhill I don't think it changed, but can you file a new issue if this is still a problem? |
where to add? |
which python file? |
@lious68 are you running a Ray script or Ray Tune etc? Anyway this issue should have been fixed in the more recent Ray versions. |
Some Ray client users are likely seeing an issue similar to #7084. Inside a container, connecting to localhost: fails but connecting to 127.0.0.1: succeeds. Changing Ray client to use 127.0.0.1 for localhost connection / serving should fix the issue.
…ray-project/ray#7084), now it works containerized
What is the problem?
I am building a Docker image with my branch and am unable to start the dashboard. Node 13.x is installed. The issue appears to be a port conflict. Perhaps there is something already listening on 8265?
Reproduction (REQUIRED)
Here is the Dockerfile I'm using, which is based off base-deps:
Running any tune experiment produces the warning.
The text was updated successfully, but these errors were encountered: