Created attachment 589086 [details] tcp: lookup proxy.golang.org on 8.8.8.8:53: dial udp 8.8.8.8:53: connect: network is unreachable Latest kubectl needs some go packages, thus fails to build without network access under the portage chroot environment
which version of golang are you using?
Manuel, It's the latest one in the moment dev-lang/go-1.13, which is apparently was updated today (05.09.2019). I guess the reason the kubectl build package stopped building is actually in go version!
Seems like kubectl doesn't support golang 1.13 at the moment... FEATURES="-network-sandbox" emerge --nodeps kubectl still won't build More info: https://github.com/kubernetes/kubernetes/issues/78845#issuecomment-501447560
Similar issue here: * Package: sys-cluster/kubectl-1.15.3 * Repository: gentoo * Maintainer: mrueg@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU * FEATURES: compressdebug network-sandbox preserve-libs sandbox userpriv usersandbox >>> Unpacking source... >>> Source unpacked in /tmp/portage/sys-cluster/kubectl-1.15.3/work >>> Preparing source in /tmp/portage/sys-cluster/kubectl-1.15.3/work/kubectl-1.15.3 ... >>> Source prepared. >>> Configuring source in /tmp/portage/sys-cluster/kubectl-1.15.3/work/kubectl-1.15.3 ... >>> Source configured. >>> Compiling source in /tmp/portage/sys-cluster/kubectl-1.15.3/work/kubectl-1.15.3 ... make -j6 -l4 -j1 -C src/k8s.io/kubernetes WHAT=cmd/kubectl GOFLAGS=-v make: Entering directory '/tmp/portage/sys-cluster/kubectl-1.15.3/work/kubectl-1.15.3/src/k8s.io/kubernetes' make[1]: Entering directory '/tmp/portage/sys-cluster/kubectl-1.15.3/work/kubectl-1.15.3/src/k8s.io/kubernetes' go: bitbucket.org/bertimus9/systemstat@v0.0.0-20180207000608-0eeff89b0690: Get https://proxy.golang.org/bitbucket.org/bertimus9/systemstat/@v/v0.0.0-20180207000608-0eeff89b0690.mod: dial tcp [2a00:1450:4001:81b::2011]:443: connect: network is unreachable +++ [0917 01:26:51] Building go targets for linux/amd64: ./vendor/k8s.io/code-generator/cmd/deepcopy-gen go: bitbucket.org/bertimus9/systemstat@v0.0.0-20180207000608-0eeff89b0690: Get https://proxy.golang.org/bitbucket.org/bertimus9/systemstat/@v/v0.0.0-20180207000608-0eeff89b0690.mod: dial tcp [2a00:1450:4001:81b::2011]:443: connect: network is unreachable !!! [0917 01:26:51] Call tree: !!! [0917 01:26:51] 1: /tmp/portage/sys-cluster/kubectl-1.15.3/work/kubectl-1.15.3/src/k8s.io/kubernetes/hack/lib/golang.sh:715 kube::golang::build_some_binaries(...) !!! [0917 01:26:51] 2: /tmp/portage/sys-cluster/kubectl-1.15.3/work/kubectl-1.15.3/src/k8s.io/kubernetes/hack/lib/golang.sh:854 kube::golang::build_binaries_for_platform(...) !!! [0917 01:26:51] 3: hack/make-rules/build.sh:27 kube::golang::build_binaries(...) !!! [0917 01:26:51] Call tree: !!! [0917 01:26:51] 1: hack/make-rules/build.sh:27 kube::golang::build_binaries(...) !!! [0917 01:26:51] Call tree: !!! [0917 01:26:51] 1: hack/make-rules/build.sh:27 kube::golang::build_binaries(...) make[1]: *** [Makefile.generated_files:200: _output/bin/deepcopy-gen] Error 1 make[1]: Leaving directory '/tmp/portage/sys-cluster/kubectl-1.15.3/work/kubectl-1.15.3/src/k8s.io/kubernetes' make: *** [Makefile:557: generated_files] Error 2 make: Leaving directory '/tmp/portage/sys-cluster/kubectl-1.15.3/work/kubectl-1.15.3/src/k8s.io/kubernetes' * ERROR: sys-cluster/kubectl-1.15.3::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=sys-cluster/kubectl-1.15.3::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-cluster/kubectl-1.15.3::gentoo'`. * The complete build log is located at '/tmp/portage/sys-cluster/kubectl-1.15.3/temp/build.log'. * The ebuild environment file is located at '/tmp/portage/sys-cluster/kubectl-1.15.3/temp/environment'. * Working directory: '/tmp/portage/sys-cluster/kubectl-1.15.3/work/kubectl-1.15.3' * S: '/tmp/portage/sys-cluster/kubectl-1.15.3/work/kubectl-1.15.3'
Same for kubectl-1.16.0.
Could it be the sandbox preventing outgoing connections?
I hope it is, because it should!
(In reply to Kobboi from comment #7) > I hope it is, because it should! At face value, this means that kubelet ebuild is meaningless, right? Could you elaborate? Basically the expectation is that if we have an ebuild in portage, that ebuild allows you to install something. If "it should" prevent the package installation, what's the whole point? It should come with indication to deal with the specific case, isn't it?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b35e587dc63def0a4cba3937b2c6471ece047fef commit b35e587dc63def0a4cba3937b2c6471ece047fef Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2019-10-05 04:36:11 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2019-10-05 04:36:49 +0000 sys-cluster/kubectl: fix compile with go-1.13 Closes: https://bugs.gentoo.org/693548 Closes: https://bugs.gentoo.org/695676 Package-Manager: Portage-2.3.76, Repoman-2.3.17 Signed-off-by: Zac Medico <zmedico@gentoo.org> sys-cluster/kubectl/kubectl-1.15.3.ebuild | 1 + sys-cluster/kubectl/kubectl-1.15.4.ebuild | 1 + sys-cluster/kubectl/kubectl-1.16.0.ebuild | 1 + 3 files changed, 3 insertions(+)
