-
Dear, I am trying to set up a network test environment via containerlab. (We use Cumulus Linux in production) name: DWlab1 topology: links: When I launch the containerlab deploy, I get this error message: INFO[0000] Containerlab v0.32.0 started goroutine 40 [running]: Have you ever encountered the case with cx images ? Could I have missed something? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 12 replies
-
Hi Try to Set the runtime to docker with name: ... Also maybe @networkop knows if something has changed in ignite |
Beta Was this translation helpful? Give feedback.
-
AFAIR, all ignite dependencies should be baked into containerlab and statically pinned. I'll test locally to confirm |
Beta Was this translation helpful? Give feedback.
-
So as it was discovered in #1039 there are issues with ignite that appear after we upgraded some packages.
|
Beta Was this translation helpful? Give feedback.
-
Hi
Try to Set the runtime to docker with
name: ...
topology:
default:
runtime: docker
…On Tue, 27 Sep 2022 at 11:04, Bben ***@***.***> wrote:
Dear,
I am trying to set up a network test environment via containerlab. (We use
Cumulus Linux in production)
After installing the prerequisites, I created a simple topology file.
name: DWlab1
topology:
nodes:
spine-test-01:
kind: cvx
image: networkop/cx:4.3.0
leaf-test-01:
kind: cvx
image: networkop/cx:4.3.0
leaf-test-02:
kind: cvx
image: networkop/cx:4.3.0
links:
- endpoints: ["spine-test-tbt-01:swp1", "leaf-test-tbt-01:swp51"]
- endpoints: ["spine-test-tbt-01:swp2", "leaf-test-tbt-02:swp51"]
- endpoints: ["leaf-test-tbt-01:swp49", "leaf-test-tbt-02:swp49"]
When I launch the containerlab deploy, I get this error message:
INFO[0000] Containerlab v0.32.0 started
INFO[0000] Parsing & checking topology file: DWlab1.clab.yml
INFO[0000] Creating lab directory: /srv/lab/DWlab01/clab-DWlab1
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x68 pc=0x1ff0e26]
goroutine 40 [running]:
github.com/weaveworks/ignite/pkg/apis/ignite.(*VM).SetKernel(...)
***@***.***/pkg/apis/ignite/helpers.go:18
github.com/srl-labs/containerlab/runtime/ignite.(*IgniteRuntime).StartContainer(0xc00062aed0,
{0x32c0a60, 0xc000b12300}, {0xc000617760?, 0x1c?}, 0xc00070ca80)
github.com/srl-labs/containerlab/runtime/ignite/ignite.go:178 +0x2a6
github.com/srl-labs/containerlab/nodes/cvx.(*cvx).Deploy(0xc0005caec0,
{0x32c0a60, 0xc000b12300})
github.com/srl-labs/containerlab/nodes/cvx/cvx.go:82 +0x76
github.com/srl-labs/containerlab/clab.(*CLab).scheduleNodes.func1(0x580525?,
0xc00057e120, 0xc000502fd0?, {0x32c5b30, 0xc000092f90})
github.com/srl-labs/containerlab/clab/clab.go:308 +0x3e7
created by github.com/srl-labs/containerlab/clab.(*CLab).scheduleNodes
github.com/srl-labs/containerlab/clab/clab.go:339 +0x145
Have you ever encountered the case with cx images ? Could I have missed
something?
Thanks for your help
—
Reply to this email directly, view it on GitHub
<#1036>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLKV5OSG3ZCNGI5GYNDLF3WAK2BNANCNFSM6AAAAAAQWSDJSA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
So as it was discovered in #1039 there are issues with ignite that appear after we upgraded some packages.
Unfortuntely we can't revert the package upgrade, so for now the ignite is out of support. cvx uses have two options