Cannot attach specific networks to containers

[arslanabbasi]

For bug reports, please include the information below:

VIC Product version:

OVA version: 1.3.0-rc2

Deployment details:

Environment where the OVA is deployed

Steps to reproduce:

Actual behavior:
There is no option to choose a specific networks when spawning containers from public repositories or containers tab in the VIC management portal. However, options are available when using templates. In the attached screenshots above, there is only a field called network mode. Setting this field to 'none' or 'host' results in the errors displayed in the screenshot above

Expected behavior:
The user should be able to choose networks, container network or bridge networks, when spawning containers from VIC management portal

Logs:

Additional details as necessary:
Please let me know if any additional information is required

[andrewtchin]

Issue moved to vmware/admiral #230 via ZenHub

[andrewtchin]

@arslanabbasi Thanks for your report. I have moved this to the Admiral project where it will be investigated.