fail to run start-container.sh

[Jekinnnnnn]

error message :

zeegin@zeegin-Virtual-Machine:~/hadoop-cluster-docker$
 ./start-container.sh
start hadoop-master container...
start hadoop-slave1 container...
start hadoop-slave2 container...
Error response from daemon: Container ebcfe89abd2ffa3c038b6960d279e95e3b3e2426cd002406422facfd8c09b04b is not running

docker info:

zeegin@zeegin-Virtual-Machine:~/hadoop-cluster-docker$ docker info
Containers: 3
 Running: 0
 Paused: 0
 Stopped: 3
Images: 1
Server Version: 1.12.6
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 18
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host overlay bridge null
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.8.0-46-generic
Operating System: Ubuntu 16.04.2 LTS
OSType: linux
Architecture: i686
CPUs: 1
Total Memory: 998.4 MiB
Name: zeegin-Virtual-Machine
ID: 4TFL:RFFY:DZIF:5ATO:OJRP:5RAD:HLXT:X6ZH:VIJN:426D:7WXK:V6JG
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 127.0.0.0/8

This issue seems like this one : https://github.com/kiwenlau/hadoop-cluster-docker/issues/2

But still failed after reboot

[NeezerGu]

I have problem just like you.And I fount that something occupied 8088 ports. I stop that, then run ./start-container.sh Everything is OK

[Jekinnnnnn]

@arthasgxy thanks for your reply. I check the ports , but there's nothing occupied 8088 :(

[huhu-jin]

我也有这样的问题

NAME="Ubuntu"
VERSION="14.04.4 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.4 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

Containers: 4
 Running: 2
 Paused: 0
 Stopped: 2
Images: 2
Server Version: 17.04.0-ce
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 33
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: 
containerd version: 422e31ce907fd9c3833a38d7b8fdd023e5a76e73
runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228
init version: 949e6fa
Security Options:
 apparmor
Kernel Version: 4.2.0-27-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 5.795GiB
Name:
ID: AAER:ASLQ:AHHM:S74E:SDIC:6UNH:FJQQ:TPJE:RUZB:7MAO:5ESH:5EGX
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Registry Mirrors:
 https://jxus37ad.mirror.aliyuncs.com/
Live Restore Enabled: false

[Yangxulei]

我也遇到这样的问题，端口也没有被占用，重启docker也不行。如何解决了，困扰半天了。

[wuliangshun]

I solve the problem by add 'sudo' : 'sudo ./start-container.sh'

[qiwihui]

you need to create docker network before run start-container.sh

sudo docker network create --driver=bridge hadoop