Community
Chat Logs
Friday, July 31, 2026
- phaleththere is no automatic dns resolution for podman containers on freebsd
- phaleththat leads back to netavark not being a thing on freebsd
- blueholy cow
- phalethcodeberg.org is down
- phalethlooks like podman is useless without netavark
- bluecodeberg sucks
- phalethalright, I'm gonna look into NixOS
- blueheh
- phalethfor FreeBSD I guess we should wait until podman 6 is there
- bluewe need superarch asap
- bluewhere's the guy who is working on them
- phalethI should also look into repopack code itself until that happens
- blueya
- phalethhow is superarch going to help? netavark is non-optional component for podman 6 and it's only compatible with linux
- bluebecause superarch will package podman 6
- blueso that will solve your netavark
- phalethyeah, but if something is not compatible there is not much to do
- bluepodman 6 doesn't need netavark no?
- phalethit does, it's not optional anymore
- bluewait so why are we waiting for podman 6 on freebsd?
- phalethwe can go back to thinking about freebsd later, I've documented the setup here https://gitea.repopack.app/repopack/provision/src/branch/master/podman/host/freebsd.md
- bluek
- phalethpodman 5 has other means to run on freebsd instead of netavark, but those are not good enough
- phaleththe automated dns resolution is not a thing and also podman networks are not really isolated from each other
- phaleththat means for now it's better to stick with linux
- blueso podman is now effectively only for linux? holy cow
- phalethyeah
- bluethat's crazy
- phalethwell, podman on freebsd is experimental, so I've done enough of experimenting for now :)
- blueha
- blue"Podman 6.0 and later requires porting Netavark to FreeBSD to replace older CNI networking plugins"
- blueoof
- phalethwe should still use freebsd to be the single point of failure for custom domains resolutions, but we need to test if CNAME record is good enough to obtain a cert from letsencrypt ore zerossl
- phalethor*
- bluemhm