Juju MAAS netwoking with custom bridge inside service

[lithium]

One of my service deployed with juju needs to run docker, after docker installation finish network "docker0" is created.

After that, all relation with another service get private-address of docker0 bridge

e.g.

$ juju add-relation myservice:db postgresql:db

$ juju debug-hooks postgresql/0

root@juju-machine-9-lxc-0:/var/lib/juju/agents/unit-postgresql-0/charm# relation-get
private-address: 172.17.42.1

juju status output:

http://paste.ubuntu.com/11393867/

Networks inside unit with docker installed:

http://paste.ubuntu.com/11393890/

Also if i want to ssh to unit

$ juju ssh servicename/0
Warning: Permanently added '192.168.1.114' (ECDSA) to the list of known hosts.

and hang there.

This happend to me in MAAS and local KVM.

[lithium (rudicba)]

Here some juju.network log of unit:

2015-05-27 17:21:13 DEBUG juju.network network.go:283 "lxcbr0" has addresses [10.0.3.1/24 fe80::74db:8cff:fe18:31c9/64]
2015-05-27 17:21:13 DEBUG juju.network network.go:255 not filtering address local-machine:127.0.0.1 for machine
2015-05-27 17:21:13 DEBUG juju.network network.go:255 not filtering address local-cloud:192.168.1.132 for machine
2015-05-27 17:21:13 DEBUG juju.network network.go:251 filtering "lxcbr0" address 10.0.3.1/24 for machine
2015-05-27 17:21:13 DEBUG juju.network network.go:255 not filtering address local-cloud:172.17.42.1 for machine
2015-05-27 17:21:13 DEBUG juju.network network.go:255 not filtering address local-machine:::1 for machine
2015-05-27 17:21:13 DEBUG juju.network network.go:259 addresses after filtering: [local-machine:127.0.0.1 local-cloud:192.168.1.132 local-cloud:172.17.42.1 local-machine:::1]
2015-05-27 17:21:13 INFO juju.worker.machiner machiner.go:94 setting addresses for machine-21 to ["local-machine:127.0.0.1" "local-cloud:192.168.1.132" "local-cloud:172.17.42.1" "local-machine:::1"]