startup-config overwritten

[ewall-cauc]

Description

I am encountering an issue where no shutdown commands inside a startup-config (.partial) file are ignored by Cisco IOL nodes in Containerlab.

Despite explicitly configuring the interfaces to be enabled, they remain in an administratively down state after deployment.

Steps to Reproduce

1. I defined an initial config snippet in router-1.partial:

interface Ethernet0/2
description test
no shutdown

2.I referenced this file in my Containerlab topology YAML under startup-config.

3.After doing a clab deploy, I logged into the router's console.

When running show ip interface brief, the interface Ethernet0/2 is down:
Interface IP-Address OK? Method Status Protocol
Ethernet0/2 unassigned YES unset administratively down down

And checking show running-config reveals that the interface is explicitly shutdown:

interface Ethernet0/2
description test
shutdown

It seems like the no shutdown command is being overwritten or ignored during the boot/provisioning phase. Has anyone encountered this with Cisco IOL images in clab? Any help would be appreciated!

[hellt]

did you define this link in the topology links section?

[ewall-cauc]

of course, i define links in topology, here is clab yaml file and startup-config.

collapsed-backbone.clab.yaml
dhcp-server-init.sh

router-1.partial.txt
router-2.partial.txt
switch.partial.txt