Getting ValueError: scheme unix is invalid

[docker]

Getting ValueError: scheme unix is invalid

[aronasorman]

Seems like it's for an old version of docker and expecting a tcp socket, while newer ones mount on /var/run/docker.sock.

[tekknolagi]

@aronasorman Shouldn't be the case. I get this on 0.7.4. Unless you mean that fig expects older versions?

[frankscholten]

I am having the same issue with Docker 0.7.5

[dazzag24]

I am seeing the same issue with docker 0.7.5:
Client version: 0.7.5
Go version (client): go1.2
Git commit (client): c348c04
Server version: 0.7.5
Git commit (server): c348c04
Go version (server): go1.2
Last stable version: 0.7.5

[aanand]

Right, I'm pretty sure this is because we're using a websocket to attach, and the websockets library doesn't support unix:// URLs. Not entirely surprising.

We needn't really be using websockets at all, except that I'm seeing some odd extra bytes in the output when using a raw socket.

While I'm investigating, a temporary fix is to run the Docker daemon on a TCP socket instead of the standard Unix one:

docker -H 127.0.0.1:4243 -d

Fig will automatically connect to 127.0.0.1:4243 if it's open, so that should be all you need.

[tekknolagi]

I changed the DOCKER_OPS in /etc/init.d/docker, but nothing appears to have
changed.

On Mon, Jan 13, 2014 at 8:52 AM, Aanand Prasad [email protected]:

Right, I'm pretty sure this is because we're using a websocket to attach,
and the websockets library doesn't support unix:// URLs. Not entirely
surprising.

We needn't really be using websockets at all, except that I'm seeing some
odd extra bytes in the output when using a raw socket.

While I'm investigating, a temporary fix is to run the Docker daemon on a
TCP socket instead of the standard Unix one:

docker -H 127.0.0.1:4243 -d

Fig will automatically connect to 127.0.0.1:4243 if it's open, so that
should be all you need.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-32187479
.

[bfirsh]

If you're using the standard Docker Ubuntu package, try putting this in /etc/default/docker:

export DOCKER_OPTS="-H unix:///var/run/docker.sock -H tcp://0.0.0.0:4243"

[tekknolagi]

I still get the error.

On Mon, Jan 13, 2014 at 9:23 AM, Ben Firshman [email protected]:

If you're using the standard Docker package, try putting this in
/etc/default/docker:

export DOCKER_OPTS="-H unix:///var/run/docker.sock -H tcp://0.0.0.0:$DOCKER_PORT"

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-32190480
.

[aanand]

Fixed in a branch, but we're waiting on a fix to docker-py to be accepted/released; if you're feeling brave, you can follow the instructions in #10 to install patched versions of both docker-py and fig.

@tekknolagi: sorry to hear it's still not working. Could you try removing the Unix socket from the config, i.e. just putting export DOCKER_OPTS="-H tcp://0.0.0.0:4243" in /etc/default/docker?

[tekknolagi]

Well, now I get this.

[aanand]

Oh dear. Right, last thing to try: run export DOCKER_URL=http://127.0.0.1:4243 in your shell before running fig.

[bfirsh]

Can you curl localhost:4243/version?

[bfirsh]

Actually let's try and debug this step by step. After setting /etc/default/docker to:

export DOCKER_OPTS="-H unix:///var/run/docker.sock -H tcp://0.0.0.0:4243"

Run restart docker. Check ps ax | grep docker to see if Docker is running. If it isn't, it'll say why in /var/log/upstart/docker.log. If it is, try curl localhost:4243/version to see if it's listening on HTTP.

[frankscholten]

I got it working after I added DOCKER_OPTS="-H 127.0.0.1:4243" in /etc/default/docker

Fig is a great tool btw! I was looking for a Vagrant-like workflow for Docker and this fits the bill :-)

[tekknolagi]

Running that command fixed it, yes.

On Tue, Jan 14, 2014 at 11:05 AM, Frank Scholten
[email protected]:

I got it working after I changed added DOCKER_OPTS="-H 127.0.0.1:4243" in
/etc/default/docker

This is a great tool btw! I was looking for a Vagrant-like workflow for
Docker and this fits the bill :-)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-32295807
.

[tekknolagi]

I just have to export that before running the fig client.

On Tue, Jan 14, 2014 at 12:24 PM, Maxwell Bernstein
[email protected]:

Running that command fixed it, yes.

On Tue, Jan 14, 2014 at 11:05 AM, Frank Scholten <[email protected]

wrote:

I got it working after I changed added DOCKER_OPTS="-H 127.0.0.1:4243"
in /etc/default/docker

This is a great tool btw! I was looking for a Vagrant-like workflow for
Docker and this fits the bill :-)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-32295807
.

[tekknolagi]

How come I can't use the docker util if I don't change the environment variable again? Is there no way for dockerd to listen on both the socket and IP?

[dz0ny]

I see. What about check?

[tekknolagi]

Check?

On Thu, Jan 16, 2014 at 5:43 AM, Janez Troha [email protected]:

I see. What about check?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-32469258
.

[aanand]

We've released a new version that fixes this. Thanks for your help and patience, folks!

$ sudo pip install --upgrade fig

You should now be able to run docker -d without specifying a host, as Fig works just fine against the Unix socket.

Note: if you are running it on a TCP port, Fig now looks for the DOCKER_HOST environment variable (not DOCKER_URL) to maintain consistency with the official Docker client, so be sure to use that.

[tekknolagi]

Wonderful! Thanks.

On Thu, Jan 16, 2014 at 10:39 AM, Aanand Prasad [email protected]:

We've released a new version that fixes this. Thanks for your help and
patience, folks!

$ sudo pip install --upgrade fig

You should now be able to run docker -d without specifying a host, as Fig
works just fine against the Unix socket.

Note: if you are running it on a TCP port, Fig now looks for the
DOCKER_HOST environment variable (not DOCKER_URL) to maintain consistency
with the official Docker client, so be sure to use that.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-32503556
.