Through DOCKER service create SDK API can we add/drop capabilities ? #2802
Assignees
Comments
|
same problem.not support util now,i guess |
|
Hi @vickydgm I´m going to check that later today @ulyssessouza could you assign this issue to me? Thanks and have a good day :) |
feliperuhland
added a commit
to feliperuhland/docker-py
that referenced
this issue
Apr 7, 2021
ContainerSpec
Docker Engine v1.41 added `CapAdd` and `CapDrop` as part of the
ContainerSpec, and `docker-py` should do the same.
```
GET /services now returns CapAdd and CapDrop as part of the ContainerSpec.
GET /services/{id} now returns CapAdd and CapDrop as part of the ContainerSpec.
POST /services/create now accepts CapAdd and CapDrop as part of the ContainerSpec.
POST /services/{id}/update now accepts CapAdd and CapDrop as part of the ContainerSpec.
GET /tasks now returns CapAdd and CapDrop as part of the ContainerSpec.
GET /tasks/{id} now returns CapAdd and CapDrop as part of the ContainerSpec.
```
I added capabilities on docstrings, `service.create` init method and
create tests for that.
That change was mention in issue docker#2802.
Signed-off-by: Felipe Ruhland <[email protected]>
Merged
|
@feliperuhland thx for ur commit. |
|
Thanks @feliperuhland |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How can I be able to do these below capabilities add/drop functionality through Docker SDK API.
'--cap-drop ALL --cap-add NET_ADMIN --cap-add NET_RAW --cap-add MAC_ADMIN
--cap-add KILL --cap-add SYS_PTRACE --cap-add SYS_ADMIN
--cap-add NET_BIND_SERVICE --cap-add DAC_OVERRIDE
--cap-add SETGID --cap-add SETUID --user 1000',
The text was updated successfully, but these errors were encountered: