The Proxmox cluster now runs a dedicated LXC container for Coolify. The container has Ubuntu 24.04 LTS, a static address in the server network and Docker underneath Coolify. This provides the environment where I can deploy my applications next.
After setting up the cluster and firewall rules, Proxmox gets another concrete service. Coolify will handle application deployments, while Proxmox continues to manage the container and its resources.
A dedicated container for Coolify#
I created the LXC myself with pct create. I considered the community script but did
not use it; for Coolify itself, I then used the official installer.
| Setting | Value |
|---|---|
| CT ID and hostname | 120, coolify |
| System | Ubuntu 24.04 LTS |
| CPU and RAM | 4 cores, 4096 MiB RAM |
| Storage | 40 GiB on local-lvm |
| Container type | unprivileged |
| Additional features | nesting=1,keyctl=1 for Docker inside LXC |
An LXC has its own programs and system files, but uses the Proxmox host’s kernel. Docker runs the Coolify services inside that environment. The information page Understanding LXC containers explains these layers and records the setup commands. An introduction to the host already exists under Understanding Proxmox.
An address in the server network#
The container initially used DHCP and was then changed to 10.10.10.20/24.
Its gateway is 10.10.10.1, with the existing Pi-hole at 10.10.10.3 providing DNS.
The address, route and name resolution worked after the change.
The VLAN assignment mattered here. In my
network layout, Coolify belongs in
server VLAN 10. The documented hypervisor port profile already carries that VLAN
as its native VLAN, untagged. The LXC therefore connects to vmbr0 without an
additional VLAN tag. An address from the right subnet would not fix an incorrect
switch port assignment.
The existing firewall rules allow access from the work network to the server network. This local setup needs no port forwarding on the internet connection.
A locale warning before installation#
Enabling SSH repeatedly produced perl: warning: Setting locale failed.
LANG was set to en_US.UTF-8, but the matching locale was not yet available in the
fresh container. That message alone did not tell me whether SSH was running.
Installing locales, running locale-gen en_US.UTF-8 and setting the default locale
resolved it. The exact commands are on the
Coolify information page.
Coolify is installed#
The official installer then ran as root inside the LXC. It sets up Docker and the
Coolify services. The local dashboard address for this setup is
http://10.10.10.20:8000.
The installation is complete. Deploying the first application is a separate next step; this entry records the container and the Coolify installation. A dashboard domain with HTTPS and configured, tested backups are still to follow. The Coolify information page explains what the platform manages and which data needs separate backups.