You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I issue a clab redeploy command without the -t option the redeploy command destroys the lab then errors and quits before redeploying:
vscode ➜ /Users/awhitaker/network_labs/eos_lab $ sudo clab redeploy
INFO[0000] Parsing & checking topology file: eos.clab.yml
INFO[0000] Destroying lab: eos
INFO[0001] Removed container: eos-leaf1
INFO[0001] Removed container: eos-leaf3
INFO[0001] Removed container: eos-spine2
INFO[0001] Removed container: eos-leaf2
INFO[0001] Removed container: eos-spine1
INFO[0001] Removed container: eos-leaf4
INFO[0001] Removing containerlab host entries from /etc/hosts file
INFO[0001] Removing ssh config for containerlab nodes
INFO[0001] Containerlab v0.61.0 started
Error: provide a path to the clab topology file
vscode ➜ /Users/awhitaker/network_labs/eos_lab $
The behavior seems different than clab deploy which automatically finds the topology in the current folder if not specified.
The behavior I would imagine best for redeploy would be to re-provision the same topology file that was parsed during the clean-up phase. If this is expected behavior and not an issue I might suggest maybe an error before the destructive phase of the cleanup to alert a topology must be provided.
Thanks so much! Clab is great!
The text was updated successfully, but these errors were encountered:
I'm on Apple ARM but as a quick test I downloaded the amd64 version of your dood-slim image and ran with emulation then copied this new beta binary over the /usr/bin/containerlab included in the container and it now appears to redeploy correctly!
If I issue a
clab redeploy
command without the -t option the redeploy command destroys the lab then errors and quits before redeploying:The behavior seems different than
clab deploy
which automatically finds the topology in the current folder if not specified.The behavior I would imagine best for redeploy would be to re-provision the same topology file that was parsed during the clean-up phase. If this is expected behavior and not an issue I might suggest maybe an error before the destructive phase of the cleanup to alert a topology must be provided.
Thanks so much! Clab is great!
The text was updated successfully, but these errors were encountered: