From 0bb8a74fab879457f93085f4089e364733a2504d Mon Sep 17 00:00:00 2001 From: baez90 Date: Tue, 5 Apr 2022 08:32:08 +0000 Subject: [PATCH] deploy: dcb4daa7eba1d1cba34b3483cb0625a935220aa6 --- index.html | 5 +- index.xml | 96 ++++++++++++++++++- post/index.html | 3 +- post/index.xml | 96 ++++++++++++++++++- .../index.html | 56 +++++++++++ post/libvirt-podman-network-mesh/index.html | 4 +- sitemap.xml | 2 +- tags/index.html | 3 +- tags/libvirt/index.html | 5 +- tags/libvirt/index.xml | 96 ++++++++++++++++++- tags/netavark/index.html | 10 ++ tags/netavark/index.xml | 91 ++++++++++++++++++ tags/netavark/page/1/index.html | 1 + tags/podman/index.html | 5 +- tags/podman/index.xml | 96 ++++++++++++++++++- 15 files changed, 549 insertions(+), 20 deletions(-) create mode 100644 post/libvirt-podman-netavark-follow-up/index.html create mode 100644 tags/netavark/index.html create mode 100644 tags/netavark/index.xml create mode 100644 tags/netavark/page/1/index.html 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 😜