Self-hosting
Running on Podman
The stack runs unchanged under Podman — with one caveat about rootless port binding.
The stack is engine-agnostic: anything that speaks Compose works. The installer
auto-detects docker compose, docker-compose, podman compose, and
podman-compose.
To drive Podman by hand, just substitute the command:
podman compose up -d # or: podman-compose up -d
In a source checkout, add -f docker-compose.yml -f docker-compose.build.yml and
--build to compile the images from the working tree.
The one difference: ports below 1024
Rootless Podman cannot bind ports below 1024 by default — which includes 80 and 443. Two ways around it.
Option A — publish on high ports
The ports are already parameterised:
curl -fsSL https://raw.githubusercontent.com/the-jk-labs/omicron/main/install.sh | HTTP_PORT=8080 HTTPS_PORT=8443 sh
# then browse http://localhost:8080
On an existing install, HTTP_PORT=8080 HTTPS_PORT=8443 podman compose up -d does
the same.
Good for local development. Not ideal for a public instance, because automatic Let’s Encrypt issuance expects 80/443.
Option B — allow low ports once
sudo sysctl net.ipv4.ip_unprivileged_port_start=80
Make it permanent by adding it to /etc/sysctl.d/:
echo 'net.ipv4.ip_unprivileged_port_start=80' | sudo tee /etc/sysctl.d/99-omicron.conf
This is the right choice for a public rootless instance: you keep the security benefit of rootless containers and still serve standard ports.
Everything else behaves identically
- Generated secrets, named volumes, and on-demand HTTPS work the same.
- Volume names are prefixed with the project name, exactly as under Docker
(
omicron_pgdata,omicron_uploads, and so on). - Every command in Backups and restore works with
podmansubstituted fordocker.
Upgrading
Same as Docker:
cd omicron
HTTP_PORT=8080 HTTPS_PORT=8443 ./install.sh # drop the ports if you allowed low ones
Under Podman the installer always recreates the containers, because podman-compose keeps a container on its old image otherwise. See Upgrading.
SELinux
On Fedora, RHEL, and derivatives, SELinux is enforcing by default. The bundled
Compose file keeps data in named volumes, and mounts its few host files (the
Caddyfile, botPolicy.yaml, the Anubis theme) with the shared z label, so
every container that needs one can read it. If you add your own bind mount,
such as a custom bot policy, give it z too:
- /home/you/botPolicy.yaml:/data/cfg/botPolicy.yaml:ro,z
Without it the container gets permission denied and keeps restarting.
Found a mistake?Edit this page on GitHub.