garden-windows job from garden-runc/1.52.0
Github source:
7251abda
or
master branch
Properties¶
garden
¶
cleanup_process_dirs_on_wait
¶A boolean stating whether or not to cleanup process state after waiting for it. If set a process can be waited for only once.
- Default
true
default_container_rootfs
¶path to the rootfs to use when a container specifies no rootfs
- Default
""
destroy_containers_on_start
¶If true, all existing containers will be destroyed any time the garden server starts up
- Default
false
dropsonde
¶
destination
¶A URL that points at the Metron agent to which metrics are forwarded. By default, it matches with the default of Metron.
origin
¶A string identifier that will be used when reporting metrics to Dropsonde.
- Default
garden-windows
image_plugin
¶Path to an image plugin binary
image_plugin_extra_args
¶An array of additional arguments which will be passed to the image plugin binary
- Default
[]
listen_address
¶Garden server listening address.
- Default
127.0.0.1:7777
log_level
¶log level for the Garden server - can be debug, info, error or fatal
- Default
info
max_containers
¶Maximum container capacity to advertise. It is not recommended to set this larger than 75.
- Default
75
network_plugin
¶Path to a network plugin binary
network_plugin_extra_args
¶An array of additional arguments which will be passed to the network plugin binary
- Default
[]
nstar_bin
¶Path to nstar binary
runtime_plugin
¶Path to a runtime plugin binary
runtime_plugin_extra_args
¶An array of additional arguments which will be passed to the runtime plugin binary
- Default
[]
tar_bin
¶Path to tar binary
- Default
C:\var\vcap\bosh\bin\tar.exe
logging
¶
format
¶
timestamp
¶Format for timestamp in component logs. Valid values are ‘unix-epoch’ and ‘rfc3339’.
- Default
unix-epoch
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/garden-windows/
directory
(learn more).
bin/garden_ctl.ps1
(fromgarden_ctl.ps1.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.