-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Improvement] Avoid using known ports for playgournd docker containers #60
Comments
+1 |
You should close this issue because the pull request is merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be improved?
Today in the docker-compose based playground, it exposes the origin port numbers in most of the cases, such as 5432, 3306, 8888, 8080. If there already has a mysql/postgres/trino or other service running, the docker-compose will fail to start, reporting "address already in use" error.
How should we improve?
As a playground running in docker, we can change the exposed port numbers to little-used numbers, to minimize the conflict possibility.
The port includes:
5432, 3306,8888,4040,8080,8090,9001,9000,9083,50070
The text was updated successfully, but these errors were encountered: