Run Docker apps next to your sites in a hosting panel
Deploy a container image or a Compose file behind nginx with a certificate, a fixed-size volume and an exact rollback, beside your PHP sites.
An application is a site that runs a container
In KLYRN a site is a domain served by nginx from a folder. An application is a domain served by nginx from a container. Accounts, certificates, backups and resource limits work the same way for both.
You start from a template, an image, a Git repository or a Compose file. The panel ends with a review in plain words.
Deploy and roll back
klyrn container deploy shop --image ghcr.io/you/shop:2.1
klyrn container route add shop shop.example.com --port 8080
klyrn container rollback shop 7The new container comes up on a private port beside the one that is serving. nginx moves to it only after its health check passes. If it never answers, the previous release is put back.
Every release records the image digest it ran. A tag can move and a digest cannot, so a rollback is exact.
Limits the kernel enforces
Each volume is its own ext4 filesystem with a fixed size, 1 GiB by default. When it fills, that application stops writing and nothing else on the server notices.
The root filesystem of a container is read-only by default. Scratch space is a sized tmpfs. Every capability is dropped.
Memory and CPU for an account are held by its own cgroup slice, which the kernel enforces. A volume can grow online from the panel, and it never shrinks.
An application gets no Docker socket, no privileged mode and no host network. Unsafe Compose fields are refused by name, with the reason.
Ready-made apps
The 1.1.9 beta adds an app installer for Joomla, Drupal, Nextcloud, Laravel, Matomo, phpBB, MediaWiki and Grav. Each installs as the site's own account, with update tracking.
Next step
Install KLYRN with curl -fsSL https://get.klyrn.com | sudo bash and open the Applications guide. Volumes are in the backups unless you mark one excluded.