-
Notifications
You must be signed in to change notification settings - Fork 559
Port 9000 (namenode IPC) not exposed #48
Comments
This is odd. I built the image locally from HEAD of master instead of using the image from hub.docker.com and port 9000 is now exposed. I can write to HDFS using another container:
I'll delete the images and pull from hub.docker.com again to confirm the problem is only with this source. |
Confirming that the image from hub.docker.com doesn't expose port 9000. This time I used tag 2.7.1:
|
It looks like port 9000 was added by 18d968c and the 2.7.1 build doesn't have it. There are no builds more recent than 2.7.1 so if someone hits the |
I just had the same problem.
|
@Starofall, thanks for the contribution. One can also build locally using a later hash (HEAD worked for me). |
After hours of struggle I finally found this issue and this:
finally worked! Could you please change it in your container? You could save people a lot of waisted hours... |
@eximius313 this project looks abandoned. Maybe you could fork it and do the update? I haven't been using this, so I'd be a poor maintainer. |
If one wants to access HDFS from another container port 9000 needs to be exposed.
Output of
docker ps
:Output of
docker port 2ff5c8467ddc | sort -n
Contents of
/usr/local/hadoop/etc/hadoop/core-site.xml
in the container:I believe the above should be
localhost
or127.0.0.1
. Running netstat will confirm the port is bound to another IP address:The text was updated successfully, but these errors were encountered: