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

[Improvement] Avoid using known ports for playgournd docker containers #60

Open
shaofengshi opened this issue Aug 16, 2024 · 2 comments

Comments

@shaofengshi
Copy link
Contributor

shaofengshi commented Aug 16, 2024

  • 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

@FANNG1
Copy link
Contributor

FANNG1 commented Aug 16, 2024

+1

jerryshao pushed a commit that referenced this issue Aug 19, 2024
See issue description: [
#60](#60)

In this PR, I changed the port to services' non-default port (exclude
Gravitino), this will avoid conflict if user already runs a service in
local, such as mysql, pg, spark, trino, jupyter etc. I manually tested
it, works well.
@jerqi
Copy link
Contributor

jerqi commented Aug 19, 2024

You should close this issue because the pull request is merged.

FANNG1 pushed a commit that referenced this issue Aug 23, 2024
In the previous PR
(#65), xiaojin gave a
suggestion on the hive container ports, +10000 to avoid conflicts. So I
raised this PR. Has tested in my local desktop, it has no impacts on the
playground.

Related issue is:
#60
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants