Make docker update support port management as well

[notpushkin]

This was the most wanted use case in #3285. Something like:

docker update -p 80:8080 --rm-port 1234 containername
docker update -P anothercontainer # expose all unexposed ports

would do.

See the original issue for the rationale.

[sqleejan]

I also need this future

[GordonTheTurtle]

USER POLL

The best way to get notified of updates is to use the Subscribe button on this page.

Please don't use "+1" or "I have this too" comments on issues. We automatically
collect those comments to keep the thread short.

The people listed below have upvoted this issue by leaving a +1 comment:

@danpopHP

[SimoneTaliercio]

+1 It would be great to be able to change configuration on a running container!

[eromoe]

Except cpu, mem and port map. I wish below can be change too:

-e 'EXCLUDE_PORTS=5000,23333,24444'
--expose '25555'
--log-driver=syslog
--log-opt syslog-address=udp://localhost:514 \

[drinktee]

I also need this feature. I want to expose a host port when the container is existing

[rmoriz]

Until docker can apply those changes without killing and recreating a container, maybe an "-R" option can be implemented to docker update just as a wrapper for those action.

This would allow us to already use docker update (as an API) even while it's not yet "feature complete". Currently it's ugly to have some things that require a kill/rm/run but other things that can be changed using update already (different code paths).

[HorvathAkosPeter]

It is a catastrophe, that you couldn't develop this trivial feature long ago.

[jlmenut]

It's surprising that a so obvious functionality is not already present.