Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ports are not exposed. #4

Closed
julioflima opened this issue Nov 19, 2020 · 2 comments
Closed

Ports are not exposed. #4

julioflima opened this issue Nov 19, 2020 · 2 comments
Labels
question Further information is requested

Comments

@julioflima
Copy link

I have to expose the ports by -p to make work.

@accetto
Copy link
Owner

accetto commented Nov 19, 2020

Hello juloko,

the ports are exposed by the following statement in the Dockerfile:

EXPOSE ${VNC_PORT} ${NO_VNC_PORT}

However, usually you use the -P or -p switches with the docker run command to bind them to some free TCP ports on your host system. Usually I prefer the -P switch, which binds all ports exposed by the container to the first free ports on the host system.

Cheers,
accetto

@accetto accetto added the question Further information is requested label Nov 19, 2020
@accetto accetto closed this as completed Nov 19, 2020
@julioflima
Copy link
Author

Sorry, only after I realized this. Thanks for explain everything so well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants