Use Digi Remote Manager to deploy and run containers

Note Container support must be enabled in Digi Remote Manager. Contact your Digi sales representative for information.

In Remote Manager, create a Configuration template. See the Remote Manager User Guide for instructions.
1. For the Settings step:
  - Click Import from device and import settings from an appropriate device.
  - Configure a script to run the container:
    1. Click System.
    2. Click Scheduled tasks > Custom scripts.
    3. Click  to add a custom script.
    4. Click the Label checkbox and type an identifiable label for the script, for example, StartContainerScript.
    5. To ensure that the script is always running:
      1. Click the Run mode checkbox and select Interval.
      2. Click the Interval checkbox and enter a very short interval (for example, one minute).
      3. Click the Run single checkbox, and toggle on to enable.
      This will configure the device to regularly check if the script is running, but only run if it is currently not running.
    6. For Commands, type the command to run the script. The command will vary depending on how you want to run the script, and what application you want to run inside the script. For example, to run the ping command inside a container, the command would be:
```
lxc container_name /bin/ping -c 30 1.1.1.1
```
2. For the Containers step:
  1. Click  to add a container to the configuration.
    If no containers have been uploaded, or if Click  to upload a container file.
    1. Click Browse and select the container file.
    2. Type the Name of the container.
      The Name entered here must be the same name as the container .tgz file. This is absolutely necessary, otherwise the container file will not be properly configured on the local devices.
    3. (Optional) Include a version number for the container.
    4. (Optional) Select the Device Type and Firmware Version that applies to the container.
      If set, these options will limit the container to only be included in Configuration templates that match the specified device type and firmware version. If these are left blank, the container can be included in any Configuration template.
    5. Click Upload.
    6. Repeat to upload additional containers.
  2. Select one or more containers to add to the configuration.
  3. Click Done.
  4. Click Save.
  5. Click Continue.
3. For the Automation step:
  1. Click to toggle on Enable Scanning.
  2. Click to toggle on Remediate.
Run a manual configuration scan to apply the container and configuration settings to all applicable devices.
Verify that the container is running on a device:
- To verify by using device metrics:
  1. From the Remote Manager main menu, click  Management >  Devices.
  2. Click the Device ID to open the device's Details page..
  3. Click Metrics.
  4. Information about configured containers is located under the Container Details heading.
- To verify by using the Data streams page:
  1. From the Remote Manager main menu, click  Management >  Data Streams.
  2. Locate the container's data stream:
    1. Click  to search using advance filtering.
    2. Click in the search text bar and select Device ID from the menu.
    3. Type the device ID and press the Enter key.
    4. Click in the search text bar again and select Stream ID from the menu.
    5. Type container and press the Enter key.
    6. Click the Stream ID to view container status.
- To verify by using the show containers command on the local device:
  1. From the Remote Manager main menu, click  Management >  Devices.
  2. Select the device.
  3. From the Actions menu, select  Open Console.
  4. At the prompt, type show containers.

Use an automation to start the container

You can also use an automation to start a container:

Follow the steps in the previous procedure, except:
- For Run mode, select Manual.
- Do not set Interval or Run single.
Create an automation that uses a Command Line Interface step.

For the Command Line Message, use the system script start command, using the label provided for the script in the previous procedure:
```
system script start StartContainerScript
```

Once the automation has been created, you can:

Run the automation manually.
Include the automation in a Configuration template as a post-remediation or post-scan step.

When creating or editing a Configuration template, at the Automation page:
1. For Post Remediation Options, click Run Automation and select the automation.
2. For On Successful Scan Options, click Run Automation and select the automation.
Include a trigger for the automation.

When creating or editing an automation, at the Triggers page:
1. Click to enable Triggered to configure the automation to be triggered, either on a schedule or by device activity.
  1. To configure the script to be run on a schedule:
    1. Click to enable By Schedule.
    2. Click Start Time.
    3. From the calendar provided, select the date and time that the script should be started for the first time.
    4. By default, the script will run only once. Click to enable Repeat to configure the script to run on a regular basis:
      1. Type or select the number of times, and select the time period.
      2. (Optional) Click Until to select a date and time when the automation schedule will stop repeating.
  2. To configure the automation to be triggered by device activity, click to enable one or more of the following:
    - Run when a device enters the target scope
    - Run when a device in the target scope enters a maintenance window:
    - Run when a device in the target scope leaves debug mode
    Target scope refers to a device that either:
    - Is member of a group that was selected on the Target page.
    - Has a tag that was selected on the Target page.
    - Is one of the devices included on the Target page.