Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

DOCKER_HOST needs a port

See original GitHub issue

Reproduction Steps:

Running codenvy:latest via Docker and mounting the docker socket.
In the terminal of a workspace, running on codenvy/alpine_jdk8, run a docker-compose command.

EXPECTED: Works

ACTUAL: Shows an error like: docker.errors.DockerException: Bind address needs a port: ...

This issue is like https://github.com/docker/docker/issues/19813 and the fix is to update DOCKER_HOST to include the port like export DOCKER_HOST="$DOCKER_HOST:2375". Since this environment variable seems to be defined by Codenvy’s workspace, I’m reporting the issue.

Codenvy version: 5.4.1

OS and version:
Linux Ubuntu-like

Docker version: Client: Version: 17.03.0-ce API version: 1.26 Go version: go1.7.5 Git commit: 60ccb22 Built: Thu Feb 23 10:53:29 2017 OS/Arch: linux/amd64

Server: Version: 17.03.0-ce API version: 1.26 (minimum version 1.12) Go version: go1.7.5 Git commit: 60ccb22 Built: Thu Feb 23 10:53:29 2017 OS/Arch: linux/amd64 Experimental: false

Codenvy cli.log output: N/A

Issue Analytics

State:
Created 7 years ago
Comments:19 (14 by maintainers)

Top GitHub Comments

3reactions

wernightcommented, Mar 17, 2017

I was wondering about the origin of the current DOCKER_HOST which seems incorrect.

Best for now would be to unset DOCKER_HOST by default.

Yes mounting the docker sockets works, and it seems there is no way to access the host by port which would be the safest supposing one does setup TLS properly.

0reactions

TylerJewellcommented, Jul 5, 2017

I am going to close this issue as the nature of the implementation and issue will change with Che on k8s.