Chat Logs

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