Netavark and Aardvark-dns v1.14 are out. Thanks to our contributors, the Netavark release is on the bigger side and did get quite a few features. So let’s have a look; all the features assume that you are also using Podman v5.4 DHCP Hostname Netavark now sends the container hostname as part of the DHCP request.…
Use pasta’s –map-guest-addr option As of Podman 5.0 we default to “pasta” as a rootless networking application to provide network connectivity for rootless containers. Compared to our previous default, slirp4netns, pasta works a bit differently. For instance, pasta, by default, does not use Network Address Translation (NAT). This means it will copy the host address…
One longstanding problem with Podman is that your rootful containers may loose network connectivity after a while. For many users it is not be obvious what is causing such problems. Netavark configures NAT and port forwarding firewall rules. When another process is deleting our firewall rules the containers will loose connectivity. One such process is…
As written in an earlier blog by Brent we are going to replace the older CNI stack Netavark and Aardvark-dns. With Podman 5.0 on the horizon we have decided that it will be the perfect time to drop CNI support from our upstream builds. As mentioned in the prior blog post we will most likely…
Whenever you deal with networking you likely need ips and thus subnets. Podman is no different and uses some default subnets that you should be aware of. This post shows you what these are and how to change them if there is already a subnet in this range on your network. Podman network The default…
Sign up with your email address to receive updates by email from this website.