Feature #7864


Exposed ports support

Added by Daniel Lobato Garcia about 9 years ago. Updated over 8 years ago.

Target version:
Fixed in Releases:
Found in Releases:


The configuration or environment part of the wizard should show a way of adding exposed ports. The Docker Remote API supports it but Fog doesn't yet. Assume Fog does support it as I have a patch pending review.
The format for exposed ports goes like

 { "ExposedPorts" : [ "22/tcp": {}, "80/tcp": {}] } 

Yes, key is the port/protocol, value is.. nothing?

Actions #1

Updated by Vanya Jauhal almost 9 years ago

I guess we will have to let the user configure a list of exposed ports in the wizard, and apart from that we will also have to ask the users to map the ports every time they start a container ?
Because, as is apparent in the docker api documentation here( , we will have to submit a port-binding every time we start a container ?

Actions #2

Updated by Daniel Lobato Garcia almost 9 years ago

Right, probably the wizard can show this in the 'environment' step. We save that information in the db, so every time you start the container you can reutilize the ports information without prompting the user.

Actions #3

Updated by Vanya Jauhal almost 9 years ago

  • Assignee set to Vanya Jauhal
Actions #4

Updated by The Foreman Bot almost 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request added
  • Pull request deleted ()
Actions #5

Updated by David Davis almost 9 years ago

Wouldn't support for PortBindings be much more useful? Unless I am understanding it incorrectly, it seems like you can do the same thing with PortBindings that you can do with ExposedPorts.

Actions #6

Updated by Vanya Jauhal over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #7

Updated by Partha Aji over 8 years ago

  • Bugzilla link set to 1231362

Also available in: Atom PDF