D4M 17.04.0-ce-rc2-mac6 (16165): Volume labels no longer accepted in stack file #32579
The previous version of Beta worked, as does the current version of Stable.
Documentation still shows volume labels as a supported feature:
Steps to reproduce the issue:
docker stack deploy -c docker-compose.yml my_app
Describe the results you received:
invalid spec: /var/run/docker.sock:/var/run/docker.sock:z: unknown option: z
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered:
Please continue to ignore, or better yet, ignore+warn; throwing an error breaks existing stack files.
Also, this behavior should be called out in the documentation. There's no mention of swarm-specific expectations:
@thaJeztah What is the best practice for larger non-config mounts (such as the TSDB for prometheus?) I generally prefer bind mounts to volumes due to the simplicity of working with them but it seems like it will be necessary to switch to a volume when working with persistent storage in docker swarm services.
@cpuguy83 Can you elaborate on the background of the decision not to support SELinux tags in services?