-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add bridge network to running container #743
Labels
area/vsphere
Intergration and interoperation with vSphere
component/portlayer/network
component/tether
kind/enhancement
Behavior that was intended, but we want to make better
severity/4-minor
Low usability or functional impact. Often has an easy workaround.
Comments
This was referenced May 20, 2016
Already in the release notes, so removing the kind/note tag. |
This is too big and needs to be decomposed |
Blocked by vSphere guestinfo volatility bug (fixed in 6.5U1, possibly backported to a 6.0 update release). This can be considered once we no longer support versions that are impacted by this bug. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/vsphere
Intergration and interoperation with vSphere
component/portlayer/network
component/tether
kind/enhancement
Behavior that was intended, but we want to make better
severity/4-minor
Low usability or functional impact. Often has an easy workaround.
Where #703 covers the personality portion of
network connect
and the application to stopped containers, this issue adds support for running containers. The workflow is:This issue is for doing so with the IPAM segregation based bridge networks only, not the mapped vSphere networks that require a PCI hotadd of a new vNIC.
The text was updated successfully, but these errors were encountered: