Che: docker fails when starting a workspace

[aleksei-burlakov]

Merry christmas and happy New year!

When I start any workspace I have a docker error.

Reproduction Steps:

1. $ git clone https://github.com/eclipse/che.git
   $ cd che/assembly
   $ mvn clean install
   $ cd assembly-main/target/eclipse-che-5.0.0-SNAPSHOT/eclipse-che-5.0.0-SNAPSHOT/bin
   $ ./che.sh start

2. Create a new workspace and start it

Expected behavior:

It starts the workspace.

Observed behavior:

The error: Could not start workspace wksp-u18r. Reason: Start of environment default failed. Error: Error response from docker API, status: 404, message: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-f6715790d40d -j DOCKER: iptables v1.4.21: Couldn't load target 'DOCKER':No such file or directory Try 'iptables -h' or 'iptables --help' for more information. (exit status 2)

Che version: the latest
OS and version: Ubuntu 14.04
Docker version: Docker version 1.12.5, build 7392c3b

Additional information:

The host computer is behind a proxy.

• Problem started happening recently, didn't happen in an older version of Che: No
• Problem can be reliably reproduced, doesn't happen randomly: Yes

[TylerJewell]

Well it is certainly great to start that kind of cheer! Thank you.

The technique that you used to start Che is about to be removed. The only allowed way to start Che moving forward will be through a docker container. And the files in the root of the repo will be removed.

Can you test this technique? https://github.com/eclipse/che/tree/master/docs/_docs/setup

[aleksei-burlakov]

Thank you TylerJewell!

I also used docker to start che
docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v ~/che/assembly/assembly-main/target/eclipse-che-5.0.0-M9-SNAPSHOT/eclipse-che-5.0.0-M9-SNAPSHOT:/che eclipse/che start
the result was the same.

[ghost]

@aleksei-burakov that is certainly some iptables issue.

Can you manually run docker containers?

docker run -ti -P codenvy/ubuntu_jdk8 bash

Does the above command open a shell into a container?

[ghost]

Maybe threads like this one can shed some light - https://github.com/docker/docker/issues/15948

[aleksei-burlakov]

No, this command doesn't start a container. It throws

docker: Error response from daemon: driver failed programming external connectivity on endpoint focused_curran (27d9c3ebadf1ff534cc80f6a4cf38bfb789f727e2483beca56caefe0c4e4acf3): iptables failed: iptables --wait -t filter -A DOCKER ! -i docker0 -o docker0 -p tcp -d 172.17.0.3 --dport 9876 -j ACCEPT: iptables: No chain/target/match by that name.
 (exit status 1).

I restarted the docker service $ sudo service docker restart and it helped, but when I reboot the host this problem occured again. So it seems to bee a docker bug.