How to use Container Station 2?
- About Container Station
- Parts of the User Interface
- Images
- Volumes
- Containers
- Create
- Logs
- Preferences
About Container Station
Container Station integrates both LXD and Docker virtualization technologies. LXD enables you to run Linux virtual machines (including Ubuntu, Debian, and Fedora). Container Station also provides one-click deployment for many popular applications and frameworks.
Parts of the User Interface
The Container Station user interface has three main areas.

Label |
Area |
Description |
---|---|---|
1 |
Toolbar |
The toolbar displays the following buttons:
|
2 |
Menu |
The menu is divided into two sections. Tip:
You can click |
3 |
Main panel |
The main panel displays the selected screen. |
Images
Images are templates that contain a set of instructions for creating a container in Container Station.
The Images screen displays a list of images downloaded or imported into Container Station. You can view image properties such as type, version, ID, size, and creation date. You can also search for images by name, create containers from existing images, sync images with a designated registry, export images, and remove images.
Downloading an Image
If you pull an image before creating a container, Container Station displays information which you can use to configure the container later.
By default, Container Station uses the Docker Hub registry, but you can also add a new registry. For details, see Adding an Image Registry.
Container Station downloads the image from the registry.
Uploading an Image
Container Station uploads the image to the remote location.
Exporting an Image
Importing an Image
Container Station allows you to import existing images from a local computer or NAS. The supported formats are *.tar, .tar.gz, and *.tgz.
When importing a container, make sure the CPU architecture of the local device matches the remote device. For example, a container exported from a device with a 64-bit x86 CPU cannot be imported to a device with a 32-bit ARM CPU.
Container Station creates a new container based on the imported data. For details, see the following:
-
Tip:
Use the
docker import
command to import an archived container file into Container Station and create a new tag (version) for the image in the container.
Removing an Image
-
You must remove any associated containers before you can remove an image.
-
This action does not remove the original image from any image registries.
Container Station removes the image.
Volumes
Volumes store and retain data from a container and allow you to share this data outside the container.
The Volume screen displays a list of all the container volumes. It displays volume information such as driver, volume name, mount point, and label. You can prune all unused volumes, remove volumes from the list, and identify which containers are using specific volumes from this screen.
Viewing Volume Connections
Container Station opens a window that lists every container connected to the volume.
Removing all Unused Volumes
Container Station removes every unused volume.
Removing a Specific Volume
Container Station removes the specified volumes.
Containers
Containers use OS-level virtualization to consolidate and standardize software in packages that can be easily shared between devices. A container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries, and settings.
Applications are multi-container resources created using Docker Compose. This is commonly used when a container may have dependencies and require other containers to function. To run applications, you can use a YAML file to describe components and configuration files.
The Container screen allows you to view the container list, perform actions on a container, and modify some container settings.
Create
Creating a Docker Container
Before creating a Docker container, you must install or import an image into Container Station. The Create screen contains a list of recommended container images or applications.
Creating an LXD Container
Before creating a LXD container, you must install or import an image into Container Station. The Create screen contains a list of recommended container images or applications.
-
LXD containers are only supported on x86-based devices running Container Station 2.4 or later and on ARM64 devices running Container Station 2.6 or later.
-
For details on running LXD container instances, see How to Run LXD Container Instances in Container Station.
Creating a Container from an Existing Image
Container Station creates the container. For details, see Creating a Docker Container.
Creating an Application
Applications are multi-container resources created using Docker Compose. This is commonly used when a container may have dependencies and require other containers to function. To run applications, you can use a YAML file to describe components and configuration files.
Container Information
To access the container information screen go to the Container tab, and click the name of an existing container. This screen has four main areas.

Label |
Area |
Description |
---|---|---|
1 |
Container name |
Displays the container type. Tip:
If using the kata runtime, a kata icon is displayed here. |
2 |
Action buttons |
Displays the different buttons that can be used to perform an action on the container |
3 |
Container details |
Displays the following information:
Note:
Depending on the container settings, some fields may be empty. |
Exporting a Container
Exporting a container allows you to move information between devices. You cannot export an application as a single file, but you can individually export each container inside of the application.
To avoid data loss, QNAP recommends stopping a container before starting the export process.
Importing a Container
Container Station allows you to import existing containers from a local computer or NAS. The supported formats are *.tar, .tar.gz, and *.tgz.
When importing a container, make sure the CPU architecture of the local device matches the remote device. For example, a container exported from a device with a 64-bit x86 CPU cannot be imported to a device with a 32-bit ARM CPU.
Container Station creates a new container based on the imported data. For details, see the following:
-
Tip:
Use the
docker import
command to import an archived container file into Container Station and create a new tag (version) for the image in the container.
Starting a Container
Container Station starts the selected containers.
Duplicating a Container
Container Station duplicates the container. For details, see Creating a Docker Container or Creating an LXD Container.
Creating an Image from a Container
This topic explains how to create an image from an existing Docker or LXD container.
Container Station creates a new image.
Stopping a Container
Container Station stops all running processes on the selected containers. Stopped containers remain listed in Container Station until they are removed.
Restarting a Container
You can manually restart unresponsive containers.
Container Station restarts the selected containers.
Removing a Container
Container Station removes the selected containers.
Executing a Container Terminal Command
Container Station allows you to run terminal commands on a running container.
The command line terminal allows you to more easily check logs and statuses, and perform actions without using a web server.
Container Station opens a new browser window with the output from the command.
Editing an Application YAML File
Container Station allows you to combine multiple containers into an application using Docker Compose. For more information, see Docker Compose.
Container Station saves the Docker Compose file.
Logs
Container Station logs actions that are performed inside the application. You can view and filter the logs, and download a copy in a CSV file.
You can perform the following tasks:
Task |
Action |
---|---|
Filter the logs |
Click
|
Clear any existing filters to display all logs |
Click Reset Filter. |
Download the logs as a CSV file |
Click Download. |
Preferences
Managing Network Settings
The Network Settings section allows you to configure the range of available IP addresses for containers to use. There are three available bridge networks you can configure:
-
lxcbr0: Provides network access for Docker containers.
-
lxdbr0: Provides network access for LXD containers.
-
docker0: Provides network access for containers of dependent applications.
Container Station saves the network settings. You must restart Container Station for the changes to the network to take effect.
To reset the network settings, click Reset to default.
Adding an Image Registry
Container Station adds the image registry.
Configuring the Application Repository
The application repository controls the containers and applications displayed on the Create screen. By default, QNAP provides a list of common containers, but you can use a customized list from a GitHub repository instead.
- On the menu, click Preferences.
- Go to Application Repository.
- Select Custom.
- Specify the repo information.
- Specify the GitHub account name.
- Specify the GitHub repo name.
- Specify any branch information.
- Click Apply.
Container Station configures the application repository.
Downloading the Docker Certificate
A Docker certificate ensures a secure connection when accessing the Container Station Docker service from another device.
You must enable port forwarding on Docker (port: 2376) and your NAS (default port: 8080, 443).
To manually renew the Docker certificate, click Renew. Renewing the Docker certificate automatically restart all the Docker containers.
Managing Kubernetes in Container Station
Container Station includes a standalone lightweight K3s cluster and the official Kubernetes web UI (Dashboard). The K3s server is an un-configurable single-node cluster that runs locally within the Docker instance. Enabling Kubernetes allows you to deploy workloads in parallel on Kubernetes and as standalone containers.
-
The default Kubernetes API server port is 6443.
-
The available Kubernetes web UI ports are between 61000 and 62000.
-
A default admin-user account is created for Kubernetes web UI management. This account is granted administrative privileges during Kubernetes deployment.
There are several limitations to using Kubernetes in Container Station:
Area |
Limitations |
---|---|
General |
|
Networking |
|
Storage |
|
Security |
|
Advanced |
|