Submit Your Ideas

We want to hear from you - vote for the features and improvements you'd most like to see, or submit your own ideas if you don't find them already listed.

Allow Container Port Mapping Override

Right now the container port is automatically mapped to the same port on the host machine, for example PostgreSQL exposes 5432 so that's where it's mapped on the host machine.  The limitation of this is it makes it impossible to run more than one container that exposes a given port.  If an application connects to multiple PostgreSQL databases, we can't match the versions to what's in production because we can only have one PostgreSQL container running.  This could be solved by either letting us override the port that's used on localhost or allow us to address the container by name and keep the default port mapping.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 7 2018
  • Future consideration
  • Attach files