Skip to content
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.

Sign up for GitHub

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

Jump to bottom

--net=none is not supported #2108

Open
caglar10ur opened this issue Aug 23, 2016 · 5 comments
Open

--net=none is not supported #2108

caglar10ur opened this issue Aug 23, 2016 · 5 comments
Labels
area/ux component/portlayer/network 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

@caglar10ur
Copy link
Contributor 

[vagrant@devbox:/opt/go/src/github.com/vmware/vic(1578)] docker run -it --net none ubuntu
docker: Error response from daemon: [POST /scopes/{scope}/containers][500] addContainerInternalServerError  &{Code:<nil> Message:scope none not found}.
See 'docker run --help'.
@caglar10ur caglar10ur added this to the VIC GA Release milestone Aug 23, 2016
@mdubya66
Copy link
Contributor

Removing the P0. Not a test stopper at the moment.

@mhagen-vmware mhagen-vmware added the kind/defect Behavior that is inconsistent with what's intended label Aug 24, 2016
@mhagen-vmware mhagen-vmware added the impact/doc/note Requires creation of or changes to an official release note label Sep 20, 2016
@mdubya66 mdubya66 removed this from the VIC GA Release milestone Sep 20, 2016
@mdubya66
Copy link
Contributor

Moving to Icebox per 9/20 Triage

@caglar10ur caglar10ur removed the impact/doc/note Requires creation of or changes to an official release note label Nov 7, 2016
@stuclem
Copy link
Contributor

stuclem commented Nov 7, 2016

Already in the release notes, so removing the kind/note tag.

@hmahmood hmahmood removed their assignment Jan 17, 2017
@corrieb
Copy link
Contributor

corrieb commented Jul 19, 2017

This is a compatibility issue. If a customer does not want a container on a network, we should be able to honor that. --net=none is meaningful. Bumping this to medium priority

@mdubya66 mdubya66 added kind/enhancement Behavior that was intended, but we want to make better priority/p4 and removed kind/defect Behavior that is inconsistent with what's intended priority/p2 labels Oct 30, 2017
@mdubya66
Copy link
Contributor

making this an enhancement. lowering priority until we get a customer report.

@zjs zjs added severity/4-minor Low usability or functional impact. Often has an easy workaround. and removed priority/p4 labels Mar 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/ux component/portlayer/network 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.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@caglar10ur @zjs @corrieb @hmahmood @mdubya66 @stuclem @mhagen-vmware