nested lxc's within a kvm machine are not accessible
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Low
|
Unassigned |
Bug Description
When running the local provider and creating a few kvm machines we are able to deploy lxc containers within those machines, however, they are unresolvable from outside of the parent machine.
An example status output:
environment: local
machines:
"0":
agent-state: started
agent-version: 1.18.0.1
dns-name: localhost
instance-id: localhost
series: trusty
"1":
agent-state: started
agent-version: 1.18.0.1
dns-name: 10.0.3.99
instance-id: poe-local-machine-1
series: trusty
containers:
1/lxc/0:
dns-name: 10.0.4.205
series: precise
hardware: arch=amd64
hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
"2":
agent-state: started
agent-version: 1.18.0.1
dns-name: 10.0.3.149
instance-id: poe-local-machine-2
series: trusty
containers:
2/lxc/0:
dns-name: 10.0.4.7
series: precise
hardware: arch=amd64
hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
services:
mysql:
charm: cs:precise/mysql-38
exposed: false
relations:
cluster:
- mysql
units:
mysql/0:
machine: 1/lxc/0
wordpress:
charm: cs:precise/
exposed: false
relations:
loadbalancer:
- wordpress
units:
wordpress/0:
machine: 2/lxc/0
open-ports:
- 80/tcp
Our environments.yaml:
default: local
environments:
local:
type: local
container: kvm
By default the kvm machines are using lxcbr0 as the network bridge. As far as I can tell the nested lxc containers are always using lxcbr0 setup within the kvm machine.
Without proper tunneling or forcing lxc to the the network-bridge defined in the juju environment it will be impossible to use nested lxc's within kvm machines.
If mixing lxc/kvms within the same environment was a supported setup we could work around this issue, otherwise, maybe having the deploy --to lxc:1 inherit the network-bridge from the juju environment.
tags: | added: cloud-installer kvm lxc |
tags: | added: addressability local-provider |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: network |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
Nested containers is not supported, though desired. As you point out the network addressability is the problem.