4 ms·
systemd-resolved can do this, though I haven't played with it too much yet. Here's a random post I just found: https://gist.github.com/brasey/fa2277a6d7242cdf4
by dnr 5y ago
systemd-resolved can do this, though I haven't played with it too much yet.
Here's a random post I just found: https://gist.github.com/brasey/fa2277a6d7242cdf4e4b7c720d42b567 https://gist.github.com/brasey/fa2277a6d7242cdf4e4b7c720d42b...
(Ha, I did the thing where I read the comments before the post, and the post describes how to do this. So what's still missing?)
- tptacek 5y agoI'm not sure how reasonable it is for us to run systemd-resolved (or systemd itself) on our VMs. We're trying to provide a clean environment for any random container to run on; we provide our own init, and that's almost the whole of it. What, I think, you really care about here is glibc's behavior. But then, you can't depend on any one libc, either.
- recuter 5y agoThe cliffs of cloud native software defined networking insanity await you: https://github.com/containernetworking/cni https://github.com/containernetworking/cni https://github.com/firecracker-microvm/firecracker-go-sdk https://github.com/firecracker-microvm/firecracker-go-sdk Firecracker, by design, only supports Linux tap devices. The SDK provides facilities to: Attach a pre-created tap device, optionally with static IP configuration, to the VM. This is referred to as a "static network interface". Create a tap device via CNI plugins, which will then be attached to the VM automatically by the SDK. This is referred to as a "CNI-configured network interface"
- YarickR2 5y agoIt's unreasonable to bring the whole cow to just get a gallon of milk . Use standalone resolver.