The Docker plugin can build a Docker image of an application, push a Docker image to a remote registry, and/or deploy the Docker image to a Docker daemon. It also launches on-demand runners to do operations remotely.
Updated 8 months ago
the authentication information to log into the docker repository
A 'source:destination' list of folders to mount onto the container from the host. A list of folders to mount onto the container from the host. The expected format for each string entry in the list is
source:destination. So for example: `binds: ["host_folder/scripts:/scripts"]
client config for remote Docker engine this config block can be used to configure a remote Docker engine. By default Waypoint will attempt to discover this configuration using the environment variables:
DOCKER_HOSTto set the url to the docker server.
DOCKER_API_VERSIONto set the version of the API to reach, leave empty for latest.
DOCKER_CERT_PATHto load the TLS certificates from.
DOCKER_TLS_VERIFYto enable or disable TLS verification, off by default.
additional TCP ports the application is listening on to expose on the container Used to define and expose multiple ports that the application is listening on for the container in use. These ports will get merged with service_port when creating the container if defined.
A map of key/value pairs to label the docker container with. A map of key/value pair(s), stored in docker as a string. Each key/value pair must be unique. Validiation occurs at the docker layer, not in Waypoint. Label keys are alphanumeric strings which may contain periods (.) and hyphens (-).
A map of resources to configure the container with, such as memory or cpu limits. these options are used to configure the container used when deploying with docker. Currently, the supported resources are 'memory' and 'cpu' limits. The field 'memory' is expected to be defined as "512MB", "44kB", etc.
environment variables to expose to the application these environment variables should not be run of the mill configuration variables, use waypoint config for that. These variables are used to control over all container modes, such as configuring it to start a web app vs a background worker