Fixing containerlab lab example

Reporters

• David Araújo (IT)

Description

Currently containerlab example seems to be using an outdated SRLinux image and deployment is very unstable and with unpredictable results.

Deployment environment

• Debian 12 (Bookworm):

Sequence of actions that resulted in the bug

• Tried to run the clab topology with sudo containerlab deploy

Document the explicit error

• Interfaces were not created at the SRLinux instances
• This does not allow to create the necessary links between devices

Expected behavior

• Create and configure interfaces at SRLinux

Fix

• Updated to a newer version of SRLinux (just a "nice-to-have")
• Increased the memory limit at the clab.yaml file for the SRL devices to 2GB. Docker was running out of memory when deploying the containers, and that was affecting the SRLinux OS.

This does seem to be environment/hardware dependent has I had conflicting results depending on the system running the tests. As an example, the original clab.yaml (with 1GB limit on SRL) deployed in a machine with a 12th gen Intel CPU running Arch OS was able to correctly deploy the topology, while another machine with a older 8th gen Intel CPU running Debian did run out of memory.