Podman suport

[hardillb]

Description

As a System Admin
I would like to be able to run FlowFuse under Podman
so that I can avoid paying Docker license fees

[hardillb]

Not looking good after 30mins testings

• nginx can't bind to 80 to 443
• Containers don't run as root, so postgresql fails to change ownership on the volumes mounted for the DB

https://github.com/containers/podman/blob/main/rootless.md

[ignitedPotato]

I'm currently running the local-dev stack as rootless podman quadlets. Works fine, but had to adapt the network so that forge finds it as this seems to be hardcoded:

[Network]
NetworkName=flowforge
Label="com.docker.compose.network=flowforge"

[hardillb]

@ignitedPotato Can you share a little bit more information please. Where did you add that Network block?

Also did you change the port mapping (or grant access to ports 80-443 some how)?

Thanks

[ignitedPotato]

Sure, I created a repository containing all relevant quadlet files (one of which is the network file I've posted already): https://github.com/ignitedPotato/flowfuse-quadlets

More about quadlets here: https://www.redhat.com/en/blog/quadlet-podman
and here: https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html

As for nginx: I use an additional reverse proxy in front of nginx which also runs inside a rootless container. To enable that container to listen on 80 and 443 I had to change the ip_unprivileged_port_start kernel parameter as such:

sysctl -w net.ipv4.ip_unprivileged_port_start=80

File ownership problems can often be fixed by adding U to mount instructions as documented here: https://docs.podman.io/en/stable/markdown/podman-run.1.html#volume-v-source-volume-host-dir-container-dir-options