Cannot attach specific networks to containers

[andrewtchin]

@arslanabbasi commented on Wed Nov 29 2017

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]

User submitted issue, moved from vic-product

[sergiosagu]

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.

This is the expected behavior. If you want to choose one or multiple existing networks when provisioning a container you do need to create a template.

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.

This looks like it could be an actual issue. @arslanabbasi - did you experience such problem with a VCH or with a standard Docker host?

[arslanabbasi]

@sergiosagu I saw this problem in a VCH.

Is there a reason for not allowing users to spawn containers with specific networks when creating containers from containers tab or public repositories? I am just trying to understand the use-case for this limitation? Or are we planning to roll out this feature in future?

[sergiosagu]

Is there a reason for not allowing users to spawn containers with specific networks when creating containers from containers tab or public repositories? I am just trying to understand the use-case for this limitation?

Originally the provisioning of containers directly from the Containers tab or Public repositories was intended more for validation purposes and/or provision containers with a minimal configuration. And then when users need a more complex deployment, maybe will multiple containers, maybe with multiple networks and maybe with multiple volumes, the option of creating (or importing) a Template is the preferred one. Moreover, templates have the benefit that they are saved (not like the single container provisioning) and users can provision them as many times as they want with a single click.

Or are we planning to roll out this feature in future?

For now we haven't thought about enhance the single container provisioning, again, since the templates provide more flexibility. But it's good to have feedback like yours so that we can reconsider the single container provisioning options.