# Containerlab topology

GitHub topic for repositories containing Containerlab topology files, enabling discovery of community-shared network labs.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Sunsetting netlab Vagrant/libvirt provider

DevFeed: [Sunsetting netlab Vagrant/libvirt provider](<https://devfeed.tech/articles/sunsetting-netlab-vagrant-libvirt-provider-34925.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/09/sunsetting-vagrant-libvirt/>)

Published: 2026-09-17T05:51:00Z

Content type: article

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Vagrant](<https://devfeed.tech/topics/vagrant.md>), [Infrastructure as code](<https://devfeed.tech/topics/infrastructure-as-code.md>), [Orchestration](<https://devfeed.tech/topics/orchestration.md>), [Containerlab topology](<https://devfeed.tech/topics/clab-topo.md>), [Oracle-VM-VirtualBox](<https://devfeed.tech/topics/vm-box.md>)

Tags: [change](<https://devfeed.tech/tags/change.md>), [containers](<https://devfeed.tech/tags/containers.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [vagrant](<https://devfeed.tech/tags/vagrant.md>), [virtualbox](<https://devfeed.tech/tags/virtualbox.md>)

### AI overview

The netlab project is sunsetting its Vagrant/libvirt provider after the vagrant-libvirt plugin became effectively unmaintained and HashiCorp announced the closure of Vagrant Cloud by the end of 2026. Existing support and tests will remain for now, but no new libvirt features or device integration tests are planned; containerlab will become the primary orchestration path.

### Source excerpt

When I started the netlab project, Vagrant was the go-to tool if you wanted to build a virtual environment described in a text configuration file (an idea popularized as infrastructure-as-code). It wasn't ideal for what we were doing, but a tool rarely does a great job when used far away from its intended use case. netlab initially supported Vagrant with VirtualBox, quickly adding support for KVM/libvirt through the vagrant-libvirt plugin. Life was good... until it wasn't. Read more ...

## Worth Reading: Lab as Code (containerlab and netlab)

DevFeed: [Worth Reading: Lab as Code (containerlab and netlab)](<https://devfeed.tech/articles/worth-reading-lab-as-code-containerlab-and-netlab-11372.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/04/worth-reading-lab-as-code/>)

Published: 2026-04-28T06:26:00Z

Content type: article

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Containerlab topology](<https://devfeed.tech/topics/clab-topo.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [networking](<https://devfeed.tech/topics/networking.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [network](<https://devfeed.tech/tags/network.md>), [worth-reading](<https://devfeed.tech/tags/worth-reading.md>)

### AI overview

The article recommends an in-depth description of managing network labs as code with containerlab and netlab. It also reports that issues documented in that post led to fixes in netlab release 26.04, including BGP advertisement support, dual-stack BGP origination, static discard routes, clearer documentation, and corrected node and plugin behavior.

### Source excerpt

@sjhloco wrote an excellent in-depth description of how you can use containerlab and netlab to manage your labs as code. He also documented a few netlab shortcomings (one of which caused a crash); fortunately, I found his blog post (admittedly over a year later) and fixed most of them in release 26.04: Read more ...

## Ansible 12.0 breaks netlab Jinja2 templates; netlab 25.09-post1 pins Ansible to 11.10 or lower

DevFeed: [Ansible 12.0 breaks netlab Jinja2 templates; netlab 25.09-post1 pins Ansible to 11.10 or lower](<https://devfeed.tech/articles/fatal-ansible-release-12-0-breaks-netlab-jinja2-templates-11242.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/09/netlab-25-09-post1/>)

Published: 2025-09-14T17:25:00Z

Content type: release

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Ansible](<https://devfeed.tech/topics/ansible.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Containerlab topology](<https://devfeed.tech/topics/clab-topo.md>)

Tags: [ansible](<https://devfeed.tech/tags/ansible.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [core](<https://devfeed.tech/tags/core.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [installation](<https://devfeed.tech/tags/installation.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [pypi](<https://devfeed.tech/tags/pypi.md>), [release](<https://devfeed.tech/tags/release.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>)

### AI overview

Ansible 12.0 requires ansible-core 2.19, whose Jinja2 templating changes broke netlab's Containerlab configuration file template. netlab 25.09-post1 checks the Ansible core version and pins installations to Ansible 11.10 or lower, with the install command available for downgrading.

### Source excerpt

On September 9th, the ansible release 12.0 appeared on PyPi. It requires ansible-core release 2.19, which includes breaking changes to Jinja2 templating. netlab Jinja2 templates rely on a few Ansible Jinja2 filters; netlab thus imports and uses those filters, and it looks like those imports pulled in the breaking changes that consequently broke the netlab containerlab configuration file template (details). netlab did not check the Ansible core version (we never had a similar problem in the past), and the installation scripts did not pin the Ansible version (feel free to blame me for this one), which means that any new netlab installation created after September 9th crashed miserably on the simplest lab topologies. This is the workaround we implemented in netlab release 25.09-post1 (released earlier today): Read more ...