Open lostdave opened 1 month ago
Hi @lostdave containerlab/vrnetlab do not modify the contents of the provided startup config.
The way it works with junos is an disk with the startup-config is mounted to the VM, and junos should read the config from it
https://github.com/hellt/vrnetlab/blob/master/vjunosswitch/docker/make-config.sh
I suppose you should check the contents of that disk to verify that the encrypted string is there as it was in the yaml file
buuuut, I think what could have happened is that containerlab tried to expand variables :D $6
, etc
Would you mind to try using the startup-config with a file, and not as embedded multiline string to confirm this theory?
Sorry ....slow to get back to this one..travel and training stuff.... i will have a look in the next couple of weeks and see what is going on
Steps to reproduce: Created a topology that included some Junos vSwitch images -> Added a block config in the topology file -> the resultant encrypted password (if if contained
.
or/
characters) would truncate.What winds up happening is the encrypted password appears as
".QdM.Nvz1fDDYhnwb27cMSXJmXxS23ti50z/liD3obqPRYs5UKHVbKFRtqZO.AoXJIVR6Um17RFfSwWm1"
ContainerLab Version 0.56.0