-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get capabilities to work in Docker swarm. #9853
Comments
Thanks for the report, but I think you need to file this in docker/cli not here. This project is just an upstream to us. |
Noted |
@stephen-turner Reopening this one; looks like this is a bug in the Docker Desktop API proxy not passing through options that were added in API v1.41; see docker/cli#2893 (comment) for reproduction steps |
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Is it fixed yet? |
Looks to be fixed (tested on Docker Desktop for Mac 3.2.2), using the reproduction steps from docker/cli#2893 (comment) docker stack deploy -c- through_proxy <<'EOF'
version: "3.9"
services:
haveged:
image: nginx:alpine
cap_add:
- NET_ADMIN
EOF Check if the capabilities were set on the service: docker service inspect --format=pretty through_proxy_haveged | grep -1 Capabilities
Image: nginx:alpine@sha256:e20c21e530f914fb6a95a755924b1cbf71f039372e94ac5ddcf8c3b386a44615
Capabilities:
Add: CAP_NET_ADMIN |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
I am trying to test the capabilities feature specified in docker/cli#2687
docker stack deploy -c havege.yml havege
Expected behavior
I expected to see
NET_ADMIN
or some sort of capabilityActual behavior
No capabilities shown.
Information
Steps to reproduce the behavior
havege.yml
fileThe text was updated successfully, but these errors were encountered: