che: Starting eclipse che with parameters in docker outputs "You are missing a mandatory parameter"

Reproduction Steps:

I am trying to run eclipse che following the documentation. Upon providing the command :

docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v /tmp/docker eclipse/che start

Always provides this output:

INFO: Welcome to Eclipse Che!
INFO:
INFO: You are missing a mandatory parameter:
INFO:    1. Mount 'docker.sock' for accessing Docker with unix sockets.
INFO:    2. Or, set DOCKER_HOST to Docker's daemon location (unix or tcp).
INFO:
INFO: Mount Syntax:
INFO:    Start with 'docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock' ...
INFO:
INFO: DOCKER_HOST Syntax:
INFO:    Start with 'docker run -it --rm -e DOCKER_HOST=<daemon-location> ...'

Which I do not understand as I am explicitly providing the same parameters.

OS and version:

Ubuntu 16.04

I am new to docker. Point to note that I am not the sudo user, my user just have been added to docker group.

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 36 (1 by maintainers)

Most upvoted comments

I have the same issue when I follow the instructions here:

$ docker run -it eclipse/che start

INFO: Welcome to Eclipse Che!
INFO: 
INFO: You are missing a mandatory parameter:
INFO:    1. Mount 'docker.sock' for accessing Docker with unix sockets.
INFO:    2. Or, set DOCKER_HOST to Docker's daemon location (unix or tcp).
INFO: 
INFO: Mount Syntax:
INFO:    Start with 'docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock' ...
INFO: 
INFO: DOCKER_HOST Syntax:
INFO:    Start with 'docker run -it --rm -e DOCKER_HOST=<daemon-location> ...'

Neither using sudo, nor using nightly, nor sudo chmod 777 /var/run/docker.sock makes a difference. The environment variable $DOCKER_HOST is undefined in my shell.

However, this full command does work:

$ docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock \
  -v ~/test/:/data eclipse/che start

OS: Linux Mint 18.1 Cinnamon 64-bit Docker: 1.13.0 build 49bf474 (info)

+20

Virtlink on Feb 1, 2017

@virtlink - your execution is expected. We already require docker sock or docker host to be added to run. We provide the simpler syntax in our docs to simplify how people get started. You provide the simple syntax first and then we guide you to add the other mounts.

TylerJewell on Feb 1, 2017

Using --privileged option solved my problem.

taoxuau on Nov 14, 2017

Thanks - please open new issue if you can provide diagnostics on the system. We have our CI systems create fedora instances on Digital Ocean for testing, and so we know it works…

TylerJewell on Feb 4, 2017

Hmm, that is a curious situation. It’s hard to say - as this would sound like an issue with how Docker was configured on your OS. Was the Docker daemon configured by someone else on the system?

TylerJewell on Feb 4, 2017

@TylerJewell - My problem looks very similar to virtlink’s. Unfortunately I don’t understand your closing comment regarding sysadmin. What’s the way forward?

ioadler on Feb 4, 2017

Closing this issue as we know that it is a sysadmin issue now.

TylerJewell on Feb 1, 2017