Create container page should show all exposed ports from dockerfile

[ghost]

Every image has dockerfile details. In that section user can see which ports image expose and which volumes.
When user want create container from image should see those ports by default, currently this sections in empty be default, the same with volumes

Dockerfile details

Ports configuration (should contains ports from dockerfile details), default empty:

Volumes configuration (should contains volumes from dockerfile details), default empty:

Currently user needs to open dockerfile details in new tab to see which ports and volumens need mapping when creating new container from image

[deviantony]

Agree, that would be a nice enhancement.

Some notes about the UX:

• This feature should be enabled only when selecting an existing image on the node (in the typeahead component)
• When selecting another image, existing ports should be removed

[StoicPerlman]

Would anyone be open to the idea of adding a checkbox that gives the option to map container ports to the same host port.

By default the I believe publish all exposed ports just maps to a random host port. Very often I find myself just mapping 80:80, 443:443 for local development. If I already have these defined in the docker file it would be nice to have that checkbox to automap.

[ncresswell]

I agree. We should offer this checkbox for all deployments, stacks, services, containers, and templates. Rgds, Neil Cresswell On 13/01/2018, at 4:22 AM, Sam Kleiner <[email protected]<mailto:[email protected]>> wrote: Would anyone be open to the idea of adding a checkbox that gives the option to map container ports to the same host port. By default the I believe publish all exposed ports just maps to a random host port. Very often I find myself just mapping 80:80, 443:443 for local development. If I already have these defined in the docker file it would be nice to have that checkbox to automap. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_1534-23issuecomment-2D357266615&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=HOiszU9l0ajfw0GyA0IqoXqCDbjhKaTqUpvNegDj6Cw&s=EbIWb--yivN0mss3SISeXw67JGhiXnlJPeAY-iHowGo&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlTJ-5FKKwB0M4lpU99HFvUxljl5Rt9ks5tJ3iggaJpZM4RM6Tt&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=HOiszU9l0ajfw0GyA0IqoXqCDbjhKaTqUpvNegDj6Cw&s=jSbwK18YgTSMcz9u_Jnjzkb9OO9A3d328AF0XBrkWWY&e=>.