Skip to content
This repository has been archived by the owner on Jun 18, 2022. It is now read-only.

Volume labels not persisted across swarm nodes #213

Open
rutherfordjw opened this issue Jun 2, 2017 · 4 comments
Open

Volume labels not persisted across swarm nodes #213

rutherfordjw opened this issue Jun 2, 2017 · 4 comments

Comments

@rutherfordjw
Copy link

Reproduce

docker volume create --driver convoy --label com.docker.ucp.access.label=KIRBY kirbyVolume

Original volume will have the label, while the duplicated volumes across the swarm nodes will not.

~/D/c/ucptechopsnp ❯❯❯ docker volume inspect kirbyVolume
[
    {
        "Driver": "convoy",
        "Labels": null,
        "Mountpoint": "/",
        "Name": "kirbyVolume",
        "Options": {},
        "Scope": "local"
    }
]

System Info

Docker version

Server:
 Version:      17.03.0-ce
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   3a232c8
 Built:        Tue Feb 28 08:10:07 2017
 OS/Arch:      linux/amd64
 Experimental: false

Host

Red Hat Enterprise Linux Server release 7.3 (Maipo)

Convoy

convoy version v0.5.0

Ask

It appears the convoy daemon doesn't support labels, which is probably why docker volumes across the hosts are created without them. We need to be able to restrict access to the volume in Docker UCP using the access label.

@yasker
Copy link
Member

yasker commented Jun 2, 2017

I don't think we support label now, I can look into it.

Which driver you're using? NFS?

@rutherfordjw
Copy link
Author

We're using NFS

@chrisfelix82
Copy link

Any updates on this? Thanks. Also what other docker volume plugins supporting NFS shared mounted to the host would you recommend to use?

@thiagolsfortunato
Copy link

+1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants