VMWare provider container networking not working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
# What I did
1. In VMWare, set "promiscuous mode", "MAC address changes" and "forged transmits" to "allowed" on the virtual switches.
2. setup a controller on vmware with container-
3. create container
# Result
Container is not accessible.
ifconfig output: http://
It does seem as if the bridge is added correctly:
```
bridge name bridge id STP enabled interfaces
br-ens192 8000.005056a41506 no ens192
vethB20SMK
lxdbr0 8000.000000000000 no
```
+------
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+------
| juju-f87094-0-lxd-0 | RUNNING | | | PERSISTENT | 0 |
+------
full systemd log from that unit: http://
# Original discussion
- https:/
(this is case #5)
description: | updated |
Changed in juju: | |
milestone: | 2.9-beta1 → 2.9-rc1 |
I presume that you did have DHCP running on the network that ens192 was connected to (presumably that was how ens192 got the 10.10.137.58 that we ended up assigning to br-ens192).
Can you go into the container and grab a copy of /etc/network/ interfaces
We would expect that eth0 should be configured as DHCP, but its possible we did something wrong and it would be configured as "manual", but no actual IP was assigned.