swarm_manager job from docker/25
Github source:
0c96d2d9
or
master branch
Properties¶
docker
¶
tls
¶Use TLS
- Default
false
tls_cacert
¶Trust only remotes providing a certificate signed by the CA given here
tls_cert
¶TLS certificate file
tls_key
¶TLS key file
tls_verify
¶Use TLS and verify the remote
- Default
false
env
¶
http_proxy
¶HTTP proxy that Docker should use
https_proxy
¶HTTPS proxy that Docker should use
no_proxy
¶List of comma-separated hosts that Docker should skip connecting to the proxy
swarm
¶
discovery
¶Swarm discovery string (ie: consul:///, etcd://,/, zk://,/, [nodes://],
discovery_options
¶Swarm discovery options
- Default
[]
swarm_manager
¶
advertise
¶Address of the Swarm Manager joining the cluster. Other Swarm Manager(s) MUST be able to reach the Swarm Manager at this address.
api_enable_cors
¶Enable CORS headers in the remote API
- Default
false
debug
¶Enable debug mode
- Default
false
filters
¶Filters to use [health, port, dependency, affinity, constraint]
- Default
- health - port - dependency - affinity - constraint
heartbeat
¶Time in second between each heartbeat
- Default
20s
listen_address
¶Listen address
- Default
0.0.0.0
log_level
¶Log level (options: debug, info, warn, error, fatal, panic)
- Default
info
overcommit
¶Overcommit to apply on resources
- Default
"0.5"
port
¶Listen port
- Default
"2375"
replication
¶Enable Swarm manager replication
- Default
false
replication_ttl
¶Leader lock release time on failure
- Default
30s
strategy
¶Placement strategy to use [spread, binpack, random]
- Default
spread
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/swarm_manager/
directory
(learn more).
bin/job_properties.sh
(frombin/job_properties.sh.erb
)bin/swarm_manager_ctl
(frombin/swarm_manager_ctl
)config/docker.cacert
(fromconfig/docker.cacert.erb
)config/docker.cert
(fromconfig/docker.cert.erb
)config/docker.key
(fromconfig/docker.key.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.