The --expose option didn't work

Bug #1650964 reported by hongbin on 2016-12-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

$ zun create --image nginux --name test --expose 80
$ zun show test
| status | Error
| status_reason | Docker internal error: 409 Client Error: Conflict ("Conflicting options: --expose and the network mode (--expose)").

The reason is that we passed --net=none when creating a Docker container (see the sandbox proposal). Therefore, --expose is not supported anymore. We should not pass --expose to the Docker daemon.

hongbin (hongbin034) on 2016-12-18
Changed in zun:
status: New → Triaged
importance: Undecided → High
prameswar (prameswar) on 2016-12-20
Changed in zun:
assignee: nobody → prameswar (prameswar)
prameswar (prameswar) on 2016-12-21
affects: zun → python-higginsclient
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers