Hello Jeff,
In case of “VNC” is running with session one on inside the container and one user working on his session.
But, user two want work on the same container… how does it work’s in that time.
when container it expose with only port or mention all will exposed…
Every new VNC session having different port number
EX:- Larry is http://192.168.0.10:5801
Moe is 192.168.0.10:5802
Curly is 192.168.0.10:5803
How to resolve those kind issues as a Docker Administator?
Good Bill,
There is the way from Docker, where we use “-P” (upper case “P”)to auto mapping to host from container. In that case, why can’t have option for auto EXPOSE.
And there is option to expose port while starting the container. also…
docker run -i --expose=22 b5593e60c33b bash
if EXPOSE port (extra) it simple Reserve only, no use of those port’s it right?
Your better bet will probably be to simply create new containers for each time a new service is needed. All of your containers would have a vnc service running internally on the VNC port, and then you would allocate new ports each time you started a new server.
docker run -d -p 5801:5800 --name vnc1 myvnc
docker run -d -p 5802:5800 --name vnc2 myvnc
Since you are asking about running multiple VNC sessions in the same container, do you need each connection to have access to some common resource? If you want your users to have access to common files, then you could put all of those files into a common volume.
Sir , i am not able to create new topic or post it in general discussions , can you assist me in this.
Dear All,
Topic:- postgres in docker container
I created a docker image (named masterimage) using base as ubunto16.04
installed java,spark,python3.6,hadoop,hive.
then in its container installed postgresql on it but while entering psql with postgres user its giving error related with perl given below
“Can’t locate strict.pm: /usr/local/lib/x86_64-linux-gnu/perl/5.22.1/strict.pm: Permission denied at /usr/bin/psql line 19.
BEGIN failed–compilation aborted at /usr/bin/psql line 19.”
i tried perl updation, uinstalled it reinstalled but every time getting same error.
Since exposing (in the context of Docker containers) is not port forwarding, just a metadata, this is not the same effect.Your answer still can help someone, I just wanted to leave this note here for the future readers, because this topic could be confusing for beginners. Maybe for others too.