[15:45] <jrwren> ya know what would be really useful... a howto guide for dealing with/debugging ubuntu-cloudimg systems/containers.
[15:46] <jrwren> because when something goes wrong, and all your usual utilities aren't there becuase it is a minimal system, it is really annoying.
[15:46] <jrwren> TIL: the `ip` command isn't even installed.
[15:46] <jrwren> like... how do you even determine your own ip address???
[15:58] <cmaloney> whut?
[15:59] <cmaloney> Are they running busybox?
[18:28] <jrwren> no, it still has /bin/dash, but it is stripped to run containers and so only has minimal tools. not even systemd AFAICT, because a container doesn't need an init system
[18:30] <jrwren> it makes sense, but I do wish there were ways... I should have cat /proc/net/fib_trie
[18:31] <jrwren> but I didn't think of it at the time.
[18:45] <cmaloney> That feels like waiting for a cactus to grow to scratch your back
[18:51] <jrwren> lul
[19:06] <jrwren> i ultimately fixed my problem... hte problem was me... :)
[19:16] <cmaloney> uh huh
[19:17] <cmaloney> "I had not queried the network card firmware directly. How could I be so daft?!"
[19:26] <jrwren> oh no. i didn't really need to know the IP. I needed to fix docker DNS resolution. my local bind was denying queries from that docker network.
[19:26] <jrwren> this is what i get for having a convoluted DNS config including BIND using views fronting iphole.
[19:27] <jrwren> i basically route DNS requests to get the results I want. It works great, but when something isn't configured right, it doesn't.
[19:29] <cmaloney> heh