Security

A Voxeltron host runs a privileged daemon. Treat host access, build isolation, and release verification as parts of the same security boundary.

Docker group access

The voxeltron user is a member of the docker group. Docker group membership is root-equivalent on the host: a member can start a privileged container, mount host paths, and change host state. Only trusted operators should be able to log in as or run code as the voxeltron user.

Do not add application users to the docker group. Keep untrusted workloads in Voxeltron containers or cells, not in shell access on the host. Review host accounts, sudo rules, and SSH keys after installation.

Host trust boundary

Access to the host's Docker socket or the daemon's data directory is equivalent to root access. Only trusted host operators may access either. Docker labels and metadata stored on disk are trusted host state. They do not form a security boundary between tenants.

Tenants act through the authenticated API. The daemon supplies project and volume ownership metadata on the server, using the authenticated caller's permissions. Tenants must not receive Docker socket access or access to the daemon's data directory.

Build isolation

Voxeltron rejects a Dockerfile build when its source context plus resulting image exceeds the 10 GiB max_disk default. The [build] section inconfiguration changes the disk limit and network mode.

Voxeltron does not configure BuildKit memory or CPU limits. As an operator option, create a dedicated builder withdocker buildx create --name voxeltron-builder --driver docker-container --driver-opt memory=2g --driver-opt cpu-quota=200000, then select it with docker buildx use voxeltron-builder.

build.network = "bridge" is the default because package installation normally needs registry access. Docker bridge networking alone does not block the cloud metadata service at 169.254.169.254, so where nftables is available the installer adds an nftables table,inet voxeltron_egress, that drops traffic from Docker bridges (docker* and br-*) and the Firecracker bridge (vxbr*) to 169.254.0.0/16,fe80::/10 and fd00:ec2::254. It covers builds and running apps, andvoxeltron-egress-firewall.service reloads it at boot. A drop-in fornftables.service reapplies it whenever nftables starts, reloads or stops, because each of those flushes the whole ruleset.vxl bootstrap installs it too, vxl daemon upgrade adds it to hosts installed before it existed, andsudo vxl-admin node harden installs the same rule on a host set up another way. If the host has no nftables, the block is not added: the installers and vxl printmetadata egress block NOT installed: nftables missing or a similar warning. Then install nftables and runnode harden, or set build.network = "none" and provide dependencies without network access. Containers on the host network are not covered.

Release signature

Release public key: RWTK4dWYTyVbrgcV0LOIXqg6p6RQECLoyMXoLGZt6e9NcOzW33vpwu7+, minisign key ID AE5B254F98D5E1CA, also at/release-key.txt. Check it against the key the installer prints, or follow thebinary verification procedure.