diff --git a/index.html b/index.html index 06cab6c..f92c3ff 100644 --- a/index.html +++ b/index.html @@ -1,7 +1,10 @@ 1533B4dC0.deSkip to main content

Libvirt & Podman: network 'mesh'

Disclaimer: I tested all this with Podman 3.x even though Podman 4.0 is already announced but the CNI driver is still available with Podman 4.0 and as soon as I get my hands on 4.0 I’ll give Netavark a try, too! +Archive

Libvirt & Podman: follow up for Podman 4.0 and netavark

This is a follow up post to “Joining libvirt VMs and Podman container in a common network”. Therefore I won’t cover all the basics again and how to configure libvirt because nothing’s changed on that side. +Podman 4.0 Podman 4.0 comes with a completely new network stack replacing the previous CNI stack: +Netavark Aardvark There are great resources that explain the backgrounds of both tools and I don’t think I could describe it better than the folks implementing it 😄 so if you’re interested have a look at the aforementioned article or the release post.

Libvirt & Podman: network 'mesh'

Disclaimer: I tested all this with Podman 3.x even though Podman 4.0 is already announced but the CNI driver is still available with Podman 4.0 and as soon as I get my hands on 4.0 I’ll give Netavark a try, too! When playing around with containers and VMs one might ask if it’s possible to bring VMs and containers into a common network segment. I see ‘why the hell would I need a VM anyway when already having containers’ or something similar I almost see on your face 😜