You can find the App Containers at System → Apps → Containers.
A Container is the actual App. On the overview page you can see all Containers in the system and if they are running or not. If a container is running it will display an info icon in the first column. When hovering over this icon with the mouse, it will display all used ports by the container.
You can get the logoutput of the container or connect to the containers screen if it is running. You can also start, stop, restart, delete or edit a container.
Be aware that most container settings can not be changed after creating it. You must delete and recreate the container.
17.4.1. Container Options¶
Name so you can identify the container
Image that the container should be based On
Start if you want it to start right away after creation
CPUs you can limit the container to a certain number of CPUs if you like
RAM Limit to limit the amount of memory
Restart Policy if the app should start automatically
Auto Remove if the app should be deleted when it finishes running
Hostname if you want to set a custom hostname inside the container
Interactive is necessary for containers that need user input and output. For example if you start debian as a container you want to enable this option.
Command if the container can execute commands at startup. For debian it would be good to start /bin/bash here.
Temporary FS if you want to mount a RAM Filesystem inside the container.
Networking can be enabled or disabled
IP and MAC you can set a custom MAC address here as well as IP Adresses. If not set one will be allocated for you. IP Adresses can only be in the Bridge App range.
Environment Variables can be created here. Each environment variable consists of a key and value pair.
Volumes that you created can be mounted inside the container here. Enter the path inside the App/Container where it should be mounted to and if it is read/write.
Devices if you want to add a device like a USB connector to the container.