| redir | hackedbellini: how did you setup lxd? | 01:09 |
|---|---|---|
| redir | more specifically how did you setup the network bridge for lxd? | 01:10 |
| * redir eow | 01:12 | |
| hackedbellini | redir: here are my lxd-bridge and network/interfaces file: | 01:19 |
| hackedbellini | network/interfaces: http://pastebin.ubuntu.com/23326622/ | 01:20 |
| hackedbellini | lxd-bridge: http://pastebin.ubuntu.com/23326614/ | 01:20 |
| hackedbellini | and here is the full output of the bootstrap command: http://pastebin.ubuntu.com/23326644/ | 01:22 |
| hackedbellini | the strange part is that it tried to "Get https://192.168.99.4:8443/1.0". But the 192.168.99.4 is another computer (the gateway). The computer where I'm running the bootstrap has an ip of 192.168.99.3, so I would expect that it tried to "Get https://192.168.99.3:8443/1.0" instead. I don't know where he is taking that ip from... The only place it is defined | 01:25 |
| hackedbellini | is on the gateway of the br0 interface | 01:25 |
| redir | hackedbellini: I was hoping it was a simple you need to run dpkg-reconfigure -p medium lxd answer | 01:29 |
| redir | but it looks like you've done manual network setup on your system | 01:29 |
| redir | I have to run, becasue I have dinner plans an won't be back for a while. | 01:29 |
| redir | but LXD worked for me just running the reconfigure command and restarting the lxd services. | 01:30 |
| redir | no network twiddling needed. | 01:30 |
| redir | but I'm guessing you're trying to run lxd hosts on the same network as the host sysytem and gateway, rather than on it's own subnet. | 01:32 |
| redir | good luck | 01:32 |
| === _stowa_ is now known as _stowa | ||
| === rmcall_ is now known as rmcall | ||
| === marcoceppi_ is now known as marcoceppi | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!