ByteCode.News
RSS
SubmitLog in

Community

Chat Logs

Friday, July 31, 2026

  1. * phaleth joined #primate
  2. * phaleth joined #primate
  3. * phaleth joined #primate
  4. * phaleth joined #primate
  5. phaleththere is no automatic dns resolution for podman containers on freebsd
  6. phaleththat leads back to netavark not being a thing on freebsd
  7. blueholy cow
  8. phalethcodeberg.org is down
  9. phalethlooks like podman is useless without netavark
  10. bluecodeberg sucks
  11. phalethalright, I'm gonna look into NixOS
  12. blueheh
  13. phalethfor FreeBSD I guess we should wait until podman 6 is there
  14. bluewe need superarch asap
  15. bluewhere's the guy who is working on them
  16. phalethI should also look into repopack code itself until that happens
  17. blueya
  18. phalethhow is superarch going to help? netavark is non-optional component for podman 6 and it's only compatible with linux
  19. bluebecause superarch will package podman 6
  20. blueso that will solve your netavark
  21. phalethyeah, but if something is not compatible there is not much to do
  22. bluepodman 6 doesn't need netavark no?
  23. phalethit does, it's not optional anymore
  24. bluewait so why are we waiting for podman 6 on freebsd?
  25. 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
  26. bluek
  27. phalethpodman 5 has other means to run on freebsd instead of netavark, but those are not good enough
  28. phaleththe automated dns resolution is not a thing and also podman networks are not really isolated from each other
  29. phaleththat means for now it's better to stick with linux
  30. blueso podman is now effectively only for linux? holy cow
  31. phalethyeah
  32. bluethat's crazy
  33. phalethwell, podman on freebsd is experimental, so I've done enough of experimenting for now :)
  34. blueha
  35. blue"Podman 6.0 and later requires porting Netavark to FreeBSD to replace older CNI networking plugins"
  36. blueoof
  37. 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
  38. phalethor*
  39. bluemhm
  40. * phaleth joined #primate
  41. * phaleth joined #primate
  42. * phaleth joined #primate