Incorporate buildctl about nerdctl HOT 6 CLOSED

Too many dependencies? or different dependencies version?

Both

from nerdctl.

Sorry, buildctl is shelled out on purpose to avoid the Go mod hell

Thanks anyway for the suggestion

from nerdctl.

Thanks for the fast answer @AkihiroSuda !

What is the go mod hell in that case?
Too many dependencies? or different dependencies version? Something else?

from nerdctl.

We should also make some effort to reduce Go dependencies to get nerdctl accepted in apt-get
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030928

And I know nerdctl continues exploding its build dependencies.

This is yet another giant monster software.

from nerdctl.

Yeah, I have read that ticket.

I do not think their assessment is fair, but nevertheless, yeah, we can focus on reducing deps, that is a good goal.
We might also want to reduce the amount of stuff we need for testing on the "host" (for example: I do not see the point in running ipfs through systemd at the same level as nerdctl - while we are ALSO testing it inside a container)

from nerdctl.

Honestly, we might want to ask this Debian person to clarify what exactly they mean.
nerdctl has about the same number of direct go mod dependencies as containerd, so, they must be talking about something else. Maybe their concerns is about cni-plugins + rootlesskit + ... ?

Without knowing what is their problem, it is going to be hard to make them happy.

from nerdctl.