问题原文
原帖链接 · volvox · CC BY-SA 3.0
I'm looking into the notion of vault running under swarm (1.12.x).
A single container would be started with:
docker run -d --cap-add IPC_LOCK -p 8200:8200 -p 8215:8125 --name vault --volume /vagrant/vault:/vagrant/vault vault server -config=/path/to/vault.hcl
but when I want to run this in swarm as a service, there appears to be no way to specify the IPC_LOCK capability, in order to lock down encrypted swapping for the vault service in this case.
How can I set --cap-add flags when starting a swarm mode service with the docker service create command?
社区高分解答
原帖链接 · James Mishra · CC BY-SA 4.0
All of the other answers here are old. Docker 20.10.0 and newer now supports specifying capabilities for Swarm services via the docker service command line and the Docker Stack YAML file format.
On the command line, you just specify --cap-add [capability] or --cap-drop [capability].
And here is an example for adding a capability in a Docker Stack YAML file:
version: "3.9"
services:
your-service:
cap_add:
- CAP_SYS_ADMIN
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
