How to specify Volumes (map[string]struct{})?

[drnic]

Sorry for the babygopher question, but cannot find an example in the test cases or docs or google.

containers.go Config defines Volumes map[string]struct{}.

How do I pass in the equivalent to docker run -v /host/path:/inner?

struct{} seems to be the equivalent of "no value" - so I'm not sure how to pass in {"/host/path": "/inner"}

Ideas?

[drnic]

    volumes := map[string]struct{}{"/host/path:/inner": struct{}{}}

I think works.

[drnic]

Hmm, no.

[gravis]

did you try volumes := map[string]struct{}{"/host/path:/inner": {}}?

[drnic]

Same result.

Using:

volumes := map[string]struct{}{"/var/run/docker.sock:/var/run/docker.sock": {}}

BTW, I'm actually trying to pass through host's /var/run/docker.sock so below is what I'm seeing:

When I do a docker inspect I see the following:

    "Volumes": {
        "/var/run/docker.sock:/var/run/docker.sock": "/mnt/sda1/var/lib/docker/vfs/dir/daf853db006ff145addc95bc9e78a54d91bf1cd88d6b6f090266219010247e4e"
    },
    "VolumesRW": {
        "/var/run/docker.sock:/var/run/docker.sock": true
    }

Rather than the following when I manually run docker run -v /var/run/docker.sock:/var/run/docker.sock...

    "Volumes": {
        "/var/run/docker.sock": "/var/run/docker.sock"
    },
    "VolumesRW": {
        "/var/run/docker.sock": true
    }

[gravis]

Please check #132 :)
I think you're not using the right "Volumes"

[drnic]

BOOM! Thanks! Binds... not Volumes. Nope wouldn't have guessed that :D

[gravis]

I know, Docker API is sometimes a jungle, and a big piece to read (when it doesn't change too often) :)
I'm glad to see you here btw.
Cheers

[webdev]

I'm trying to do something similar, but it's not the Binds.

I'm trying to mount ssh keys from the host into the container, and trying to use

Volumes:     map[string]struct{}{
                "/myworkdir": {}, 
                "/root/.ssh": "/root/.ssh",
            },

However, I'm getting the wrong set up when inspecting the container

    "Volumes": {
        "/root/.ssh:/root/.ssh": "/mnt/sda1/var/lib/docker/vfs/dir/24aae2a54b02dd4f7312ab3a6f707d53b22edcb96e93224a028402d846d960ed",
        "/myworkdir": "/mnt/sda1/var/lib/docker/vfs/dir/730674e9b75649066af9ee92e486ab7edef8233d66fc28bc2a0249bb17124ff6"
    },
    "VolumesRW": {
        "/root/.ssh:/root/.ssh": true,
        "/myworkdir": true
    }

[Setomidor]

I suppose you've already figured this out by now, but for other people who may stumble upon this:

What you are trying to do is mixing Volumes and Binds:

• For "/myworkdir" you want to use volumes as this simply exposes this endpoint as a "non-UnionFS" mount point (in an anonymous location, in your case the thing starting /var/lib/docker/vfs/dir/..).
• For "/root/.ssh" you want to use binds as this creates a bind between the container and the fixed location "/root.ssh" on your host machine.

Send the Binds argument to the HostConfig (since this can only be done when deploying an actual container instance on an actual host), and send the Volumes argument to the container Config when creating this Container (as the exposed mount points are linked to the container, and not the instance).

This links contains a great explanation about wha volumes are and how they work: http://container-solutions.com/2014/12/understanding-volumes-docker/

[mieubrisse]

I'm having the same problem as the original poster, but I'm using named volumes rather than bind mounts. I'm confused about why the value type of Volumes is a struct{}, and what I should be passing in as the value. Should that be the Volume object that comes back from CreateVolume?