Add Container Template
Comprehensive guide to configuring Container templates, storage mounts, importing templates, Registries, and Network Endpoints.
Create or import a template here when the App Store does not have the container template you need. A Container packages a program with its required environment; this page uses Docker containers. A template stores installation settings. After creating it, install it from the App Store to create an application you can operate.
Before You Start
Obtain the image name, version tag, resource requirements, and any required environment variables, ports, storage paths, and device settings from the application provider. Do not guess values for optional items you do not need.
- Container Registry: The source storing container images. An image contains the program and environment files used to create a container. If the source is not configured yet, follow “Adding a Container Registry” below first.
- Image Tag: A label selecting an image version. The existing default is
latest; confirm which tag your application requires. - Network Endpoint: The container's network connection settings. Decide where it needs to connect and who may connect to it before choosing a mode. See the field descriptions below for restrictions.
Adding a Container Template
- Go to the Application > Template > Container page.
- Click the Add Template icon.

- Type the App Name.
- Select the Container Registry.
- Type the Image Name.
- Type the Image Tag (defaults to
latest). - Select the Network Endpoint.
- Choose the Resource Limitation.
- Configure Environment Variables (setting names and values passed to the program) as required by the application.
- Click Upload App Icon to add an icon for the application.
- Enter an App Description.
- (Optional) Configure Port Binding (port mapping): Add single ports or port ranges according to Docker requirements to map the device's external service ports to ports inside the container.
- (Optional) Configure Volumes (storage): Add storage paths to keep container data as required by Docker.
- (Optional) Configure Labels (identifying tags): Add names and values for identification and management as required by Docker.
- (Optional) Configure Commands (startup instructions): Enter commands to run inside the container as required by Docker.
- (Optional) Configure Devices (device mappings): Select the hardware devices the container needs as required by Docker.

Note: “Device” lists all devices under
/dev(the system's device path), including USB devices and serial ports. Select the devices to mount according to the application's requirements.
The service section in the screenshot also has a Service Name field for identifying the service. Fill it in for the service you are creating.
- If using Docker Compose (a way to manage multiple container services with a set of settings), add more services and repeat steps 5 through 16 for each service.
- Click the Apply button.
- Go to Application > App Store and confirm that the new template appears. Then follow Install APPs to install it.
Using an External USB Drive for a Container
To use external storage, first identify the target disk, then complete device mapping and manual mounting. Mounting makes the disk available at a path inside the container. Console is a terminal where you enter text commands.
- Select the external hard disk.
- Click Apply.

- Navigate to Application > Information > Container > Action > Console to mount the disk using command-line commands.
This page does not provide a mount command suitable for every disk. If you are unfamiliar with the command line, confirm the disk, target path, and commands with your administrator rather than guessing. Afterward, check that the container can access the disk at the intended path. Selecting the disk and applying alone does not complete the manual mounting step above.
Importing an Existing Template
Use import when you already have an App Template file. Prepare the file, name, description, and icon first.
- Go to Application > Template > Container > Import Template.
- Type the App Name.
- Type the App Description.
- Browse and select the App Template file.
- Upload the App Icon.
- Click the Apply button.

After importing, confirm the template name and description in the App Store before installing it.
Adding a Container Registry
Use this when an image source is not registered yet. Prepare the registry's server address and, if it requires sign-in, a username and password or token (an access credential).
- Go to Application > Template > Container > Registry.
- Click the Add button to add a container registry.

- Type the Registry Name.
- Enter Server Address (required). Enable insecure HTTP access is a separate optional toggle. Enable it only after confirming that this source requires unencrypted HTTP access; it is not a prerequisite for entering the server address.
- (Optional) Enter the User Name and Password/Token.
- Click the Apply button.

After saving, return to template settings and confirm that you can select the new source under Container Registry. During installation, check that the image can be retrieved.
Adding a Network Endpoint
Use this when you need custom container network settings. Network Driver determines how the container network is created. Use the options from your network plan or administrator rather than guessing values.
- Go to Application > Template > Container > Network Endpoint.
- Click the Add button to create a Network Endpoint.
- Type the Network Name.
- Select the Network Driver.
- Configure Network Driver options.
- Click the Apply button.

After saving, return to the template's Network Endpoint field and confirm that you can select the new entry. Test the required connections and restrictions after installation.
Template Field Descriptions
| Item | Description |
|---|---|
| App Name | Define a unique name for your application. |
| Container Registry | A repository for container images (e.g., Docker Hub for public repositories, or private registries). |
| Image Name | The name of the Docker image to use. An image is a read-only file used to create a container; enter the name supplied by its provider. |
| Image Tag | Version tags to manage container images. Defaults to latest. |
| Network Endpoint | Select container network settings; see the modes and access options below. |
| Resource Limitation | Limits on CPU (processing resources) and memory available to the container. Profiles: Low (0.2 CPU core + 128 MB Memory); Medium (0.5 CPU core + 512 MB Memory); High (2 CPU cores + 2 GB Memory). Note: If container requirements exceed selected resource limits, execution will fail until limits are adjusted. |
| Environment Variable | Key-value pairs used to pass user or application parameters inside containers. |
| Port Binding | Configures TCP/UDP protocol mappings for public and private ports. Setting public port to 0 assigns a random port. |
| Volumes | Filesystem mounts used to persist container data. |
| Labels | Key/value metadata: extra identifying information used for organization and management. |
| Commands | Commands executed upon container startup to initialize services or tasks. |
| Upload App Icon | Custom icon image displayed on the App Store page. |
| App Description | Brief summary explaining application features and purpose. |
Network Modes and Access Options
Bridge is the default container network mode here. Host mode is available only to the containers specified below. Preserve the connections your application needs while checking who may access it.
| Mode or option | Purpose and restrictions |
|---|---|
| Host | Reserved for Wireshark or IPsec containers. Others default to Bridge and cannot switch to Host. |
| Bridge | Default network mode. |
| Network-restriction(bridge) | Bridge mode with access rules, using the options below to manage access. |
| Allow Internet Access (Select Egress WAN) | Allows internet connectivity and selects the outgoing WAN (external network) connection. If the container has a login port, its page access is restricted and managed through Port Mapping. |
| Allow Controller Access | Allows Controller access to the container. |
| Allow LAN IP/24 Access | Restricts access to devices in the specified /24 LAN (local network) subnet. |
| Allow WAN IP Access | Restricts access to specified WAN IP addresses. |
| None | Applies no network restrictions; confirm that this matches your access requirements. |