# Deploy a new containerized application to run on the cluster

Requires node-exec::modify permission.

Endpoint: POST /v2/cluster/{clusterFQDN}/exec/container
Version: 1.0.0
Security: JWTAuthorizer

## Path parameters:

  - `clusterFQDN` (string, required)
    Node FQDN

## Request fields (application/json):

  - `command` (string)
    Command to run in the container

  - `description` (string)
    Container description
    Example: "my container"

  - `enabled` (boolean)

  - `execType` (string)
    Execution type
    Enum: "onDemand", "service", "recurring"

  - `hostname` (string)
    Container hostname
    Example: "mycontainer"

  - `id` (string)
    Container ID
    Example: "b4011aa3-d0d5-4c5c-9c0b-19095ba515d5"

  - `image` (object)
    Image

  - `image.repository` (string)
    Image repository
    Example: "mycompany.trustgrid.io/myimage"

  - `image.tag` (string)
    Image tag
    Example: "latest"

  - `name` (string)
    Container name
    Example: "mycontainer"

  - `privileged` (boolean)
    Run the container as a privileged user

  - `requireConnectivity` (boolean)
    Only start the container if the node has connectivity to the control plane. Needed for encrypted volumes.

  - `stopTime` (string)
    Grace period for container to stop when requested, in seconds
    Example: "60"

  - `useInit` (boolean)
    Indicates that an init process should be used as PID 1 in the container. Ensures responsibilities of an init system are performed inside the container (e.g., handling exit signals).

  - `user` (string)
    User name (or UID) and optionally the group (or GID) to use when starting the container.  This will override the USER specified in the image


## Response 200 fields