Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Containerlab

containerlab.dev

  • Free plan
  • Open source
  • Windows
  • macOS
  • Linux
  • Web
  • Browser extension
  • API
  • Self-hosted
8.5 Club score Visit containerlab.dev

What Containerlab is

Containerlab is a free, open-source command-line tool for building and managing container-based networking labs. Users describe a lab in a topology file, specifying nodes, links, and settings, then use the CLI to deploy, inspect, save, graph, or destroy it. Supported nodes include containerized and virtual-machine network operating systems from Nokia, Cisco, Juniper, Arista, and other vendors and projects. The project lists support for platforms such as SR Linux, XRd, cRPD, SONiC, VyOS, FRR, FreeBSD, OpenWRT, Linux containers, and generic VMs. Containerlab can launch VM-based routers through vrnetlab or boxen, and Clabernetes can run Containerlab-style topologies on Kubernetes. Optional graphical interfaces include a VS Code extension, desktop app, and web app; the desktop and web options connect to a reachable clab-api-server on a Linux host. The API server handles lab lifecycle and related file, terminal, capture, image, and inspection operations. The project also describes using lab definitions in CI systems such as GitLab CI and GitHub Actions. Documented prerequisites include a Linux server or VM, Docker, and sudo privileges for some operations.

Who it suits

Containerlab suits network engineers and teams that want to define and manage virtual network labs from the command line. Its CI use cases also fit teams that need to start topologies in automated workflows.

Good to know, and what to watch

  • Topology files define nodes, links, and settings declaratively.
  • CLI supports deploy, destroy, save, inspect, and graph.
  • Supports network OS images from multiple vendors and projects.
  • Can launch VM routers through vrnetlab or boxen.
  • Topology definitions can be used in CI systems.
  • Requires a Linux server or VM and Docker.
  • Some operations require sudo privileges.
  • Sudo-less setup can grant group members root-level privileges.

Containerlab

Free

Free and open-source

Free

Open source

Getting started

  1. Visit the Containerlab website
  2. Prepare a Linux server or VM
  3. Install Docker
  4. Provide sudo privileges for required operations
  5. Create a topology file describing nodes, links, and settings
  6. Run the Containerlab CLI to deploy the lab

Limits to check

The free Containerlab plan requires a Linux server or VM and Docker. Sudo privileges are required for some operations.

The verdict

Containerlab provides a code-driven way to create and operate network labs, with optional graphical interfaces and a wide range of supported nodes. Its Linux and Docker prerequisites, plus the privilege implications of its sudo-less setup, are worth reviewing before deployment.

Questions people ask

What does Containerlab cost?

Containerlab is free and open source. Its listed plan is free.

Which operating systems and network platforms does Containerlab support?

It runs on Linux, macOS, and Windows interfaces, with self-hosted deployment. Supported nodes include Nokia, Cisco, Juniper, Arista, SONiC, Cumulus VX, VyOS, FRR, VPP, BSD systems, OpenWRT, Linux containers, generic VMs, and more.

Can Containerlab run on Kubernetes?

Yes. Clabernetes can run Containerlab-style topologies on Kubernetes.

What is clab-api-server used for?

The clab-api-server performs lab lifecycle, file, terminal, capture, image, and inspection operations on the Linux host.

Can Containerlab be used in CI systems?

Yes. The project describes starting topologies in CI systems including GitLab CI and GitHub Actions using its single binary and code-based lab definitions.

What license does Containerlab use?

The public GitHub repository identifies the project license as BSD-3-Clause.

What the maker publishes

API
The clab-api-server performs lab lifecycle, file, terminal, capture, image, and inspection operations on the Linux host. source
API documentation
Running API servers expose Swagger and Redoc documentation and have a published API reference. source
API security
The API server authenticates host Linux users and groups, returns JWT tokens, defaults to HTTPS, and can generate self-signed certificates. source
API server
clab-api-server exposes lab operations over HTTP for automation, browser clients, desktop GUI, and shared lab hosts, embedding Containerlab as a Go library. source
CI and testing
The project describes using its single binary and code based lab definitions to start topologies in CI systems, including GitLab CI and GitHub Actions. source
CI use
The single binary and code-defined labs are intended for GitHub Actions, GitLab CI, and other CI systems. source
Company ownership
The repository says Containerlab was kick-started by Nokia engineers and supports multi-vendor platforms. source
Documentation depth
Documentation covers installation, quickstart, topology syntax, kinds, networking, commands, GUI, API server, Clabernetes, examples, releases, and developer contribution workflows. source
GUI options
The graphical interface is available as a VS Code extension, desktop app, and web app; desktop and web connect to a reachable clab-api-server. source
Integrations
Containerlab can launch VM based routers through vrnetlab or boxen integration and can run containerlab style topologies on Kubernetes through Clabernetes. source
Kinds abstraction
Platform-specific kinds hide the startup, mount, entrypoint, and command differences between network operating systems and other node types. source
Kubernetes integration
Clabernetes runs containerlab-style topologies on Kubernetes through a controller, CRDs, and the clabverter conversion tool. source
Licence
The main repository is publicly marked as BSD-3-Clause licensed. source
License
The public GitHub repository identifies the project license as BSD-3-Clause. source
Lifecycle commands
The CLI supports lab deploy, destroy, save, inspect, and graph operations. source
Lifecycle commands
The project provides deploy, destroy, save, inspect, and graph operations for lab management. source
Limit: commercial images
NetPilot reports that commercial Cisco, Juniper, Arista, Palo Alto, and Fortinet images are bring-your-own-image and may require vrnetlab builds and registry troubleshooting. source
Limit: configuration scope
NetPilot states that Containerlab wires topologies and applies supplied startup configuration but does not generate BGP, OSPF, or EVPN device configuration. source
Limit: host setup
NetPilot's independent guide says local use requires Linux, Docker, and usually root, so Containerlab does not run natively on macOS or Windows. source
Limit: throughput caveat
The VPP comparison reports that default disabled TX checksum offload and TSO on veths can make TCP or VPP throughput appear about five times slower until MTU and offloads are normalized. source
Maker founded
Nokia describes its innovation history as beginning in 1865. source
Maker headquarters
Nokia lists its head office at Karakaari 7, 02610 Espoo, Finland. source
Networking
Containerlab creates point-to-point virtual links and a managed Docker management network, with bridge, macvlan, host-link, DNS, Tailscale, and impairment options documented. source
Network OS support
Supported nodes include containerized and virtual machine based network operating systems from Nokia, Cisco, Juniper, Arista, and other vendors and projects. source

Checked against the maker's pages on 15 Oct 2026.