Consider forking weaveworks/ignite

[gaby]

Containerlab is the biggest project using weaveworks/ignite right now. The project seems to have been abandoned since weaveworks is now focused on gitops. It may be worth for containerlab to fork and at least update deps for ignite.

Rel weaveworks/ignite#971

[hellt]

Hi @gaby
We are using the fork done by @networkop. Looks like for now it does all that is needed.

[gaby]

@hellt Your go.mod still points to weaveworks though:

https://github.com/srl-labs/containerlab/blob/main/go.mod#L39

[hellt]

@gaby

containerlab/go.mod

Line 295 in 8c9b54f

replace (

[gaby]

@gaby

containerlab/go.mod

Line 295 in 8c9b54f

replace (

😁 Didn't see that. Seems like even that one still has the CNI issue. Ignite was never updated to cni v1.0.0 while containerlab does use it. Not sure if that's an issue 🤔

Just wanted to make sure that containerlab was aware of ignite being abandoned.

[hellt]

We are not using it much to be honest. Only cumulus nodes leverage ignite, and a few corner cases for Linux containers.

We wont maintain it either, all the hope is with @networkop :)

[networkop]

Yep, feel free to tag me in any ignite-related issues. I'll try to keep it alive for as long as it makes sense.