Why the exposed port range is 32768-65535, which is not the same as the range in che.properties? about che

[TylerJewell]

We narrow the range of what is exposed so that docker will start in a reasonable time. There is significant overhead for each expert port exposed.

[freewind]

Is the 32768-65535 in Dockerfile still right? Shall we make the two ranges the same?

[freewind]

I'm not sure when I start docker image, which range of port shall I use. e.g.

1. docker run -it --privileged -e DOCKER_MACHINE_HOST=159.203.201.197 -p 8080:8080 -p 49152-49752:49152-49752 codenvy/che:4.0.0-beta-5
2. docker run -it --privileged -e DOCKER_MACHINE_HOST=159.203.201.197 -p 8080:8080 -p 32768-32788:32768-32788 codenvy/che:4.0.0-beta-5

Shall I start with 49152 or 32768? Or either one is OK?

[TylerJewell]

No the internal structure is correct. The better answer is to use the --net option. We need to do more testing on that option and its performance before we make that the primary configuration.

[TylerJewell]

Start with the 32768 but both should be ok.

[freewind]

@TylerJewell Not quite understand why it's 32768, since it's only exposed in Dockerfile. Does the che program running inside the container have a way to know it? I thought it should get the sys.resources.min_port from che.properties and use 49152

[TylerJewell]

@eivantsov?

[TylerJewell]

This should explain it.
https://eclipse-che.readme.io/v4.0/docs/usage-docker#ports

range of available service ports

sys.resources.min_port=49152
sys.resources.max_port=65535

deprecated. we'll remove it from conf