ByteCode.News
RSS
SubmitLog in

Community

Chat Logs

Thursday, March 12, 2026

  1. * jreicher joined #primate
  2. * phaleth joined #primate
  3. bluehi phaleth
  4. * phaleth joined #primate
  5. bluewb phaleth
  6. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
  7. * nevet joined #primate
  8. phalethhi blue
  9. bluephaleth: btw did the rp app work for you?
  10. phalethyeah
  11. bluethat's cool, it means podman is the way to go
  12. phalethyeah, except it's supposed to be podman within podman and so the lower podmans will have to be exposed as tcp services I think in order to be reachable from host OS
  13. bluewait why podman in podman?
  14. phalethcause only that way podman is secure enough
  15. blueare you sure we need to ues podman as a security layer
  16. bluewe're using it as an abstraction layer, for now
  17. bluepodman isn't for security, anyway. that's kvm / separated dedis
  18. phalethpodman is easy to use cause it can run docker images, with qemu/kvm you have to use these cloud images otherwise the OS may not be bootable, so you loose the ability to use docker images and so you loose the ability to use an already provided build system and also already provided image layers
  19. phalethand once you can define everything as layers and not some kind of horrid monoliths while still being secure enough then you can save up on a lot of resources
  20. phalethand btw the upper podman may still need to be run as root to be able to limit resources, so single podman is a no go
  21. blueI'm just not sure perf would be great in podman in podman, no?
  22. phalethit should be as long as pasta is in use and not some net4whatever you have in the readme you wrote
  23. phalethprolly written by clanker, but it was still helpful
  24. phalethslirp4netns
  25. phalethhttps://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md#networking-configuration
  26. blueOMG GITHUB
  27. blueit's saying "Too many requests"
  28. bluesomebody burn this piece of garbage down
  29. phalethyeah, it often times does that
  30. blueI can't access what you sent
  31. blueit's blocking me
  32. blue"You have exceeded a secondary rate limit.
  33. blue"
  34. phalethhttps://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md
  35. blueyeah
  36. blueI think I have that slirp thing locally
  37. blueon the vps we can do pasta if that's the modern alternative
  38. blueI don't think it's gonna matter because I'll be using the libpod API
  39. phalethI already installed the first layer of podman on the vps, I will put podman user creds to vw later on
  40. bluethat's where haproxy is running?
  41. phalethyeah, you can just uninstall that weirdly named thing and install passt instead
  42. blueor is it running on root?
  43. phalethbut I think on archlinux podman just installs pasta automatically
  44. phalethI mean podman gets installed with pasta
  45. phalethpodman is installed on the archlinux host OS
  46. blueah ok
  47. phalethand also haproxy is
  48. blueso podman and haproxy will be the ONLY packages the root system will need?
  49. phaleththere is also the standalone buildkit, not installed via pacman, but downloaded via wget
  50. phalethcould use curl, but could not be bothered
  51. phalethand then there is of course systemd
  52. phalethbut for example in case of freebsd systemd will not be used, instead there is something else that I forgot
  53. phalethwhile podman, haproxy and buildkit are freebsd compatible
  54. bluewell as long as we stay freebsd-compat, that'd be great
  55. bluebecause superarch will have freebsd as a target
  56. blueand I intend to be using superarch servers in the future
  57. phalethok
  58. phalethI gotta go, see ya
  59. blueciao
  60. * jreicher joined #primate