We have cleanbuild now. But it's pretty common for go developers to have GOROOT set.
Is it really the only option for them to use a lxd to build? We should have a strong reason for that.
And if so, the go plugin should catch when GOROOT is set and suggest to use LXD, instead of this weird error.
We have cleanbuild now. But it's pretty common for go developers to have GOROOT set.
Is it really the only option for them to use a lxd to build? We should have a strong reason for that.
And if so, the go plugin should catch when GOROOT is set and suggest to use LXD, instead of this weird error.
So I'm leaving this open.