containerlab release .41. that came out a several days back altered a several topology attributes with no backward compatibility, breaking netlab for anybody executing a new set up. The only way out of that conundrum was to push out a new netlab launch that makes use of the new characteristics and demands containerlab launch .41. (more about that in a minute).

On a more optimistic be aware, netlab release 1.5.3 delivers a handful of fascinating attributes, such as:

I will go over the community libvirt networks in an additional weblog write-up, now I want to clarify how we’re dealing with containerlab improvements.

Root trigger: containerlab launch .41. modified the identify of management community characteristics from mgmt_ipv4/ipv4_subnet to mgmt-ipv4/ipv4-subnet with no backward compatibility or deprecation time period. Outdated topologies no extended perform, and new topologies don’t do the job with more mature variations of containerlab.

Mitigation: The only safe and sound way to offer with this transform was to improve the netlab containerlab topology template and enforce bare minimum containerlab version in the course of netlab up virtualization company exams. The netlab set up installation scripts could use an older containerlab version, but that would not aid people putting in containerlab manually (without the need of looking through the smallprint). It would also split netlab the instant a person would improve containerlab.

Beneficial side effects: netlab up and netlab down now executed a variety of commands to test the virtualization company installation. I modified individuals probes to return a with any luck ,-helpful error message when the executed command fails.

containerlab probes examine the availability of containerlab command and containerlab edition (working with a bash command that seems like line noise). libvirt probes are a lot more in depth and examine that:

  • You mounted KVM and KVM utilities like kvm-alright
  • KVM performs (for example, you have not forgotten to convert on nested virtualization)
  • You set up libvirt and built oneself a member of libvirt group
  • You installed Vagrant and vagrant-libvirt plugin.


To get extra facts and study about supplemental options included in release 1.5.3, browse the launch notes. To update, execute pip3 install --upgrade networklab. You will also have to enhance containerlab with sudo containerlab version up grade.

New to netlab? Start off with the Finding Started out doc and the installation manual.

Require support? Open up a dialogue or an concern in netlab GitHub repository. There’s also a netlab channel in networktocode Slack workforce, but you will get more quickly response time reporting your troubles in GitHub.


Source hyperlink