Quick start¶
Two Linux containers, one link, a ping across it. No network OS image to download and no license to configure.
You need one of the apps installed and connected to a Linux machine with Docker. To only look around, the browser sandbox is enough for steps 1 and 2.
name: linux-playground
topology:
defaults:
kind: linux
image: ghcr.io/srl-labs/network-multitool:latest
nodes:
client:
exec:
- ip address add 10.10.10.1/24 dev eth1
server:
exec:
- ip address add 10.10.10.2/24 dev eth1
links:
- endpoints: [client:eth1, server:eth1]
name: linux-playground
topology:
defaults:
kind: linux
image: ghcr.io/srl-labs/network-multitool:latest
nodes:
client:
exec:
- ip address add 10.10.10.1/24 dev eth1
server:
exec:
- ip address add 10.10.10.2/24 dev eth1
links:
- endpoints: [client:eth1, server:eth1]Click a node to see its definition. Show in YAML jumps to its lines in the file. The exec commands give each container an address on eth1 when it starts.
-
Get the file. Use Download YAML above and save it as
linux.clab.yml. -
Open it in your app.
Put the file in the folder you have open. Select the containerlab icon in the Activity Bar. The lab shows up under undeployed labs; open it in the topology editor.
Open Files in the left rail and upload the file to your workspace: on this computer, or on the lab host. Then open it.
Open the sandbox and import the file. You can edit and arrange it, but not deploy it.
-
Deploy. Select the green play button in the editor toolbar. Each node shows a status badge once its container is up.
-
Ping across the link. Right-click
client, choose Shell, and run: -
Change it. Add a third node from the palette, connect it, and watch the YAML update. When you are done, open the arrow next to the play button and choose Destroy. Your file stays; only the containers go away.