lxc - error on LXD container while we install JUJU gui ver. 2.0 - Ask Ubuntu
lab:
nr. 1 host ubuntu 16.04lts - lxd & zfs
nr. 2 - lxc container (maas & juju)
i've create container maas, , it's in running state
$: lxc list
+-------------+---------+--------------------+------+------------+-----------+
| name | state | ipv4 | ipv6 | type | snapshots |
+-------------+---------+--------------------+------+------------+-----------+
| xenial-maas | running | 10.20.40.29 (eth0) | | persistent | 0
i'd create lxd xenial controller juju using following command
$: juju bootstrap lxd xenial-juju --debug
after having started container
$: lxc list
+---------------+---------+--------------------+------+------------+-----------+
| name | state | ipv4 | ipv6 | type | snapshots |
+---------------+---------+--------------------+------+------------+-----------+
| juju-6f0b4e-0 | running | 10.20.40.57 (eth0) | | persistent | 0 |
+---------------+---------+--------------------+------+------------+-----------+
| xenial-maas | running | 10.20.40.29 (eth0) | | persistent | 0 |
+---------------+---------+--------------------+------+------------+------- ----+
it gives me following error:
12:37:11 error cmd supercommand.go:458 failed bootstrap model: subprocess encountered error code 1
here debug file https://paste.ubuntu.com/23450682/
while without --debug error on screen following
2016-11-09 10:16:12 error cmd supercommand.go:458 new environ: creating lxd client: https://10.20.40.254:8443/1.0: unable connect to: 10.20.40.254:8443 error failed bootstrap model: subprocess encountered error code 1
after container removed
$: lxc list
+-------------+---------+--------------------+------+------------+-----------+
| name | state | ipv4 | ipv6 | type | snapshots |
+-------------+---------+--------------------+------+------------+-----------+
| xenial-maas | running | 10.20.40.29 (eth0) | | persistent | 0
it's bug :
https://bugs.launchpad.net/juju/+bug/1633788
same problem me . juju take wrong ip address lxd node
where did able juju bootloade.
when container running can go inside container , :
iptables -t nat -a output -d ${wrong_ip} -p tcp --dport 8443 -j dnat --to-destination ${good_ip}:8443
Comments
Post a Comment