slirp4netns VS Pulumi

History likes to repeat itself:

https://github.com/rootless-containers/slirp4netns

It should not actually require root anymore - see https://github.com/rootless-containers/slirp4netns

USER root RUN curl -o /var/lib/apt/dazzle-marks/docker.gpg -fsSL https://download.docker.com/linux/ubuntu/gpg \ && apt-key add /var/lib/apt/dazzle-marks/docker.gpg \ && add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" \ && install-packages docker-ce docker-ce-cli containerd.io RUN curl -o /usr/bin/slirp4netns -fsSL https://github.com/rootless-containers/slirp4netns/releases/download/v1.1.12/slirp4netns-$(uname -m) \ && chmod +x /usr/bin/slirp4netns

Podman pods are kind of their own thing, networking wise, being under slirp4netns https://github.com/rootless-containers/slirp4netns

i foud this slirp4netns in the meantime as well. There are a bunch of other problems. with podman. I cannot use nftables and firewalld with systemd+nftables, the mentioned port-"problem" for rootless podman, ipv6 containers and some other stuff that isn't working or very config-heavy. i found a lot of github issues that are actively discussed in the past days regarding some of the mentioned topics on this post. My conclusion is that i will still use docker and will look into this in a year or so... to early imo to really switch to podman because almost no benefits to docker for me. (i want ipv6, rootless containers all the way and full nftable support)

If you are following this blog series, you should already know the benefits of using Terraform to define and deploy your AWS resources and configuration. Other IaC solutions such as AWS CloudFormation, AWS CDK, and Pulumi work the same way but differs in the programming or configuration language.

Infrastructure as Code (IaC) is an important part of any true hosting operation in the public cloud. Each of these platforms has their own IaC solution, e.g. AWS CloudFormation. But they also support popular open-source IaC tools like Pulumi or Terraform. A category of tools that also needs to be discussed is API gateways and other app-specific load balancers. There are applications for internal consumption, which can be called microservices if you have a lot of them. And often microservices use advanced networking options such as a service mesh instead of just the native private network offered by a VPC.

funny, to me systemd == no docker, no containers, just a VM.

it's my goto way to keep my programming running and have it be restarted if the vm reboots. I use VMs like "pods". I deploy code directly to the VM and run it there along with other programs. I scale up an scale down with: https://www.pulumi.com/

Pulumi — Modern infrastructure as a code platform that allows you to use familiar programming languages and tools to build, deploy, and manage cloud infrastructure.

A move like this may have an impact in other open source projects. Take Pulumi, for instance, people might avoid choosing it now that the Linux Foundation have its own IaC tool, and for newer, smaller projects it will probably be impossible to compete with a project under the Linux name.

Another alternative to writing an operator would be to rely on kustomize or https://www.pulumi.com/.

Pulumi

Would it make sense to say Dagger is to Pulumi [1], as Terraform is to Togomak?

[1]: https://www.pulumi.com/

Infrastructure as Code (IaC): Define your infrastructure using code (IaC) to automate the provisioning of resources such as virtual machines, load balancers, and databases. Tools like Terraform, Pulumi, and AWS CloudFormation can help.