Docker
docker Runs apps as containers on a Docker host.
Settings
hostDocker hostAdvancedThe Docker endpoint. Empty uses the environment, which the bundled Compose file relies on.
total_cpu_millisCPU availableAdvancedThousandths of a core Pando may allocate.
total_memory_bytesMemory availableAdvancedBytes Pando may allocate.
total_disk_bytesDisk availableAdvancedBytes of disk Pando may allocate.
pids_limitProcesses per containerAdvancedHow many processes and threads each app container may run at once, so one app cannot exhaust the host's process table. A negative number removes the limit.
network_poolApp network rangeAdvancedThe IPv4 range each app's private network takes its addresses from. A /16 holds about 4,000 apps; a wider range such as 10.208.0.0/12 holds more. "off" uses Docker's own pool, which holds about 30 networks.
network_block_bitsApp network sizeAdvancedThe size of each app's private network, as a prefix length from 24 to 29. 28 holds 13 containers; an app with more workloads than fit gets a larger network.
egress_gateway_imageEgress gateway imageAdvancedThe image an app's egress gateway runs from when its egress rules restrict anything: any image with Pando's binary at /usr/local/bin/pando. Without one, and with Pando not running in a container, apps whose egress is restricted cannot be deployed.
oci_runtimeContainer runtimeAdvancedThe runtime Docker starts apps with, by the name it is registered under in daemon.json. "runsc" (gVisor) or a Kata runtime makes this a sandboxed runtime, which host policy can require; the port and file-write checks when an app is added then cannot see inside the sandbox, so Pando asks for the port instead.