search

Segence / docker-hadoop

A Docker container with a full Hadoop cluster setup with Spark and Zeppelin
63 stars 40 forks source link

fail to start "local-cluster" on windows for docker #4

Open askme765cs opened 6 years ago

askme765cs commented 6 years ago

root@hadoop-namenode:~# service hadoop start

====== STARTING HDFS ======

Starting namenodes on [hadoop-namenode] hadoop-namenode: Warning: Permanently added '[hadoop-namenode]:2222,[172.18.0.2]:2222' (ECDSA) to the list of known hosts. hadoop-namenode: starting namenode, logging to /usr/local/hadoop/logs/hadoop-hadoop-namenode-hadoop-namenode.out : Temporary failure in name resolutionop-datanode1

saif-ellafi commented 6 years ago

It's failing for me also on the same stage, although my error is different:

====== STARTING HDFS ======
Starting namenodes on [hadoop-namenode]
hadoop-namenode: Warning: Permanently added '[hadoop-namenode]:2222,[172.18.0.2]:2222' (ECDSA) to the list of known hosts.
hadoop-namenode: starting namenode, logging to /usr/local/hadoop/logs/hadoop-hadoop-namenode-hadoop-namenode.out
: Name or service not knownstname hadoop-datanode1
: Name or service not knownstname hadoop-datanode2

Windows 10 Home + docker toolbox

Fixed slaves-config/slaves and docker-composer.yml in windows is generated with Windows EOL. Change it to Linux EOL (notepad++) and it works great

robvadai commented 4 years ago

Hi @saif-ellafi ,

was the EOL issue after you manually edited the file? The Git version should have UNIX EOL...

saif-ellafi commented 4 years ago

Yes, it's been some long time now but I had to fix the EOL manually for it to work. It was a nightmare to discover that was the actual issue though. Not even a slight clue.

robvadai commented 4 years ago

Shall we close this issue?