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
Adds support for sysctl options in docker services.
* Adds API plumbing for creating services with sysctl options set.
* Adds swagger.yaml documentation for new API field.
* Updates the API version history document.
* Changes executor package to make use of the Sysctls field on objects
* Includes integration test to verify that new behavior works.
Essentially, everything needed to support the equivalent of docker run's
`--sysctl` option except the CLI.
Includes a vendoring of swarmkit for proto changes to support the new
behavior.
Signed-off-by: Drew Erny <drew.erny@docker.com>
Copy file name to clipboardExpand all lines: api/swagger.yaml
+12Lines changed: 12 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -2750,6 +2750,18 @@ definitions:
2750
2750
description: "Run an init inside the container that forwards signals and reaps processes. This field is omitted if empty, and the default (as configured on the daemon) is used."
2751
2751
type: "boolean"
2752
2752
x-nullable: true
2753
+
Sysctls:
2754
+
description: |
2755
+
Set kernel namedspaced parameters (sysctls) in the container.
2756
+
The Sysctls option on services accepts the same sysctls as the
2757
+
are supported on containers. Note that while the same sysctls are
2758
+
supported, no guarantees or checks are made about their
2759
+
suitability for a clustered environment, and it's up to the user
2760
+
to determine whether a given sysctl will work properly in a
2761
+
Service.
2762
+
type: "object"
2763
+
additionalProperties:
2764
+
type: "string"
2753
2765
NetworkAttachmentSpec:
2754
2766
description: |
2755
2767
Read-only spec type for non-swarm containers attached to swarm overlay
0 commit comments