You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 18, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 18, 2022. It is now read-only.
Volume labels not persisted across swarm nodes #213
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.
Reproduce
docker volume create --driver convoy --label com.docker.ucp.access.label=KIRBY kirbyVolumeOriginal volume will have the label, while the duplicated volumes across the swarm nodes will not.
System Info
Docker version
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.