When trying to build a package using Bazel (e.g. conda-forge/grain-feedstock#7) with --sandbox, it's failing to connect to the local server:
│ │ + bazel clean
│ │ Starting local Bazel server and connecting to it...
│ │ ... still trying to connect to local Bazel server (52) after 10 seconds ...
My educated guess would be that you're not setting lo inside the network sandbox, and a call to ifconfig seems to confirm that. Could you please set it up after entering namespace, so that it would be possible to connect to local daemons while running them in isolation from the rest of the network stack?
Admittedly this won't help with Bazel (because apparently it's crap that needs Internet access anyway), but from my Gentoo experience, having a loopback interface is helpful for running test suites.
When trying to build a package using Bazel (e.g. conda-forge/grain-feedstock#7) with
--sandbox, it's failing to connect to the local server:My educated guess would be that you're not setting
loinside the network sandbox, and a call toifconfigseems to confirm that. Could you please set it up after entering namespace, so that it would be possible to connect to local daemons while running them in isolation from the rest of the network stack?Admittedly this won't help with Bazel (because apparently it's crap that needs Internet access anyway), but from my Gentoo experience, having a loopback interface is helpful for running test suites.