Docker port option missing

A "host" network doesn't have port mapping

Change your network to "bridge".

It isn't a host network.  It's a custom network actually.  The host part in the screenshot is just the default naming from the container maker.  It looks confusing because the container port is missing.

Same for custom networks, there is no port mapping

Oh!  OK then, I'll check that out.

 

Thanks.

Changed Status to Closed

Changed Priority to Other

So I got back to look at this and I can see quite clearly existing custom networks did have port mapping working.  Presently, if you create a new container in bridge mode first, then convert them to custom networks, the port mapping comes across.

 

Regarding the above statement that they're not meant to work - it would be obvious that e.g. the letsencrypt container example would require a lot of special routing to work if it did not have the port mapping feature available.  Clearly it is desirable to have port mapping on custom networks.

 

So I'm not sure if I'm missing something here, but either it was always quirky like this, or we lost the capability to create directly in a custom network at some point.  I feel like it's the latter - but could be wrong.

 

The below shows that my existing proxynet networks have port mapping successfully enabled.

 

Re-opening this in the hope it will be reconsidered in this context.

 

Thanks.

 

 

The only custom networks supported now are macvlan based.

Adding custom bridge networks can be done by CLI, but has no further support in the GUI other then make them selectable.

 

If you want full support of custom bridge networks, you'll need to raise a feature request.

Edited November 23, 2019 by bonienl

I think there are very few cases where one needs to edit the container port. I think we might have one container where it's needed to edit the container port. So in my opinion it would be nice to be able to when you are not using the default bridge.

You can work around it by adding a new port mapping. Then you will have access to set the container port. At least on 6.7.2.

 

 

The port mappings do work even on custom bridges. It seems to me that you are both misunderstanding each other.

Marshalleq are talking about custom bridge and bonienl are talking about setting a dedicated IP on a custom network?

 

 

 

Edited November 24, 2019 by saarg