Container
The VyOS container implementation is based on Podman as a deamonless container engine.
Configuration
Sets the image name in the hub registry
set container name mysql-server image mysql:8.0
If a registry is not specified, Docker.io will be used as the container registry unless an alternative registry is specified using set container registry <name> or the registry is included in the image name
set container name mysql-server image quay.io/mysql:8.0
Override the default entrypoint from the image for a container.
Override the default command from the image for a container.
The container and the host share the same process namespace. This means that processes running on the host are visible inside the container, and processes inside the container are visible on the host.
The command translates to “–pid host” when the container is created.
Allow host networking in a container. The network stack of the container is not isolated from the host and will use the host IP.
The command translates to “–net host” when the container is created.
Note
allow-host-networks cannot be used with network
Attaches user-defined network to a container. Only one network must be specified and must already exist.
Optionally set a specific static IPv4 or IPv6 address for the container. This address must be within the named network prefix.
Note
The first IP in the container network is reserved by the engine and cannot be used
Optionally set a custom name server. If a container network is used with DNS enabled, this setting will not have any effect.
Add custom environment variables. Multiple environment variables are allowed. The following commands translate to “-e key=value” when the container is created.
set container name mysql-server environment MYSQL_DATABASE value 'zabbix'
set container name mysql-server environment MYSQL_USER value 'zabbix'
set container name mysql-server environment MYSQL_PASSWORD value 'zabbix_pwd'
set container name mysql-server environment MYSQL_ROOT_PASSWORD value 'root_pwd'
Publish a port for the container.
set container name zabbix-web-nginx-mysql port http source 80
set container name zabbix-web-nginx-mysql port http destination 8080
set container name zabbix-web-nginx-mysql port http protocol tcp
Mount a volume into the container
set container name coredns volume 'corefile' source /config/coredns/Corefile
set container name coredns volume 'corefile' destination /etc/Corefile
Volume is either mounted as rw (read-write - default) or ro (read-only)
Mount a tmpfs (ramdisk) filesystem to the given path within the container.
Size in MB for tmpfs filesystem, maximum size is 64GB or 50% of the systems total available memory.
Set the restart behavior of the container.
no: Do not restart containers on exit
on-failure: Restart containers when they exit with a non-zero exit code, retrying indefinitely (default)
always: Restart containers when they exit, regardless of status, retrying indefinitely
This specifies the number of CPU resources the container can use.
Default is 0 for unlimited. For example, 1.25 limits the container to use up to 1.25 cores worth of CPU time. This can be a decimal number with up to three decimal places.
The command translates to “–cpus=<num>” when the container is created.
Constrain the memory available to the container.
Default is 512 MB. Use 0 MB for unlimited memory.
Add a host device to the container.
Set container capabilities or permissions.
net-admin: Network operations (interface, firewall, routing tables)
net-bind-service: Bind a socket to privileged ports (port numbers less than 1024)
net-raw: Permission to create raw network sockets
setpcap: Capability sets (from bounded or inherited set)
sys-admin: Administration operations (quotactl, mount, sethostname, setdomainame)
sys-time: Permission to set system clock
Set container sysctl values.
The subset of possible parameters are:
Kernel Parameters: kernel.msgmax, kernel.msgmnb, kernel.msgmni, kernel.sem, kernel.shmall, kernel.shmmax, kernel.shmmni, kernel.shm_rmid_forced
Parameters beginning with fs.mqueue.*
Parameters beginning with net.* (only if user-defined network is used)
Container Networks
Define IPv4 and/or IPv6 prefix for a given network name. Both IPv4 and IPv6 can be used in parallel.
Configure MTU for a given network. It is the size (in bytes) of the largest ethernet frame sent on this link.
Disable Domain Name System (DNS) plugin for this network.
Container Registry
Adds registry to list of unqualified-search-registries. By default, for any image that does not include the registry in the image name, VyOS will use docker.io and quay.io as the container registry.
Some container registries require credentials to be used.
Credentials can be defined here and will only be used when adding a container image to the system.
Allow registry access over unencrypted HTTP or TLS connections with untrusted certificates.
Registry mirror, use (host-name|address)[:port][/path]
.
If you have mirror http://192.168.1.1:8080 for docker.io, you can use docker.io/some/repo
or run podman pull docker.io/some/repo
set container registry docker.io mirror address 192.168.1.1
set container registry docker.io mirror port 8080
set container registry docker.io insecure
If http://192.168.1.1:8080 is your own registry, you can use 192.168.1.1:8080/some/repo
or run podman pull 192.168.1.1:8080/some/repo
set container registry 192.168.1.1:8080 insecure
Log Configuration
Operation Commands
Delete a particular container image based on it’s image ID. You can also delete all container images at once.
You can not delete a container image if it has more then one tag assigned, this is why there is a force option to pass down to the container image to also remove those images.
Example Configuration
For the sake of demonstration, example #1 in the official documentation to the declarative VyOS CLI syntax.
set container network zabbix prefix 172.20.0.0/16 set container network zabbix description 'Network for Zabbix component containers' set container name mysql-server image mysql:8.0 set container name mysql-server network zabbix set container name mysql-server environment 'MYSQL_DATABASE' value 'zabbix' set container name mysql-server environment 'MYSQL_USER' value 'zabbix' set container name mysql-server environment 'MYSQL_PASSWORD' value 'zabbix_pwd' set container name mysql-server environment 'MYSQL_ROOT_PASSWORD' value 'root_pwd' set container name zabbix-java-gateway image zabbix/zabbix-java-gateway:alpine-5.2-latest set container name zabbix-java-gateway network zabbix set container name zabbix-server-mysql image zabbix/zabbix-server-mysql:alpine-5.2-latest set container name zabbix-server-mysql network zabbix set container name zabbix-server-mysql environment 'DB_SERVER_HOST' value 'mysql-server' set container name zabbix-server-mysql environment 'MYSQL_DATABASE' value 'zabbix' set container name zabbix-server-mysql environment 'MYSQL_USER' value 'zabbix' set container name zabbix-server-mysql environment 'MYSQL_PASSWORD' value 'zabbix_pwd' set container name zabbix-server-mysql environment 'MYSQL_ROOT_PASSWORD' value 'root_pwd' set container name zabbix-server-mysql environment 'ZBX_JAVAGATEWAY' value 'zabbix-java-gateway' set container name zabbix-server-mysql port zabbix source 10051 set container name zabbix-server-mysql port zabbix destination 10051 set container name zabbix-web-nginx-mysql image zabbix/zabbix-web-nginx-mysql:alpine-5.2-latest set container name zabbix-web-nginx-mysql network zabbix set container name zabbix-web-nginx-mysql environment 'MYSQL_DATABASE' value 'zabbix' set container name zabbix-web-nginx-mysql environment 'ZBX_SERVER_HOST' value 'zabbix-server-mysql' set container name zabbix-web-nginx-mysql environment 'DB_SERVER_HOST' value 'mysql-server' set container name zabbix-web-nginx-mysql environment 'MYSQL_USER' value 'zabbix' set container name zabbix-web-nginx-mysql environment 'MYSQL_PASSWORD' value 'zabbix_pwd' set container name zabbix-web-nginx-mysql environment 'MYSQL_ROOT_PASSWORD' value 'root_pwd' set container name zabbix-web-nginx-mysql port http source 80 set container name zabbix-web-nginx-mysql port http destination 8080