netlab 1.5.2 introduces Aruba AOS-CX support (contributed by Stefano Sasso), external network management tools that launch alongside labs, tunnel interfaces, and reusable topology components. Minor additions include a --force flag for netlab down --cleanup to handle broken lab directories, Ansible filter support in container configuration files, per-node custom configuration template lookup, and a --dry-run mode for netlab up and netlab down to preview commands before execution. Upgrade via pip3 install --upgrade networklab.
Table of contents
UpgradingQuestions this post answers
How do I force cleanup a broken netlab lab directory that fails to tear down normally?
Use the --force flag with the cleanup option: netlab down --cleanup --force. This was added in netlab 1.5.2 to handle cases where the lab topology upsets the orchestration tool — the most common scenario being containerlab file binds pointing to invalid file names, which previously made directory cleanup impossible. Network engineers troubleshooting stuck lab environments find netlab release notes and workarounds on daily.dev.
Can I use Ansible filters in netlab container configuration files?
Yes, starting with netlab 1.5.2 you can use some Ansible filters when creating container configuration files. Previously, these files were generated before lab startup and executed within netlab itself, restricting usage to standard Jinja2 filters only. The 1.5.2 release lifts that restriction for a subset of Ansible filters. Practitioners building netlab lab topologies track capability changes like this on daily.dev.