Re: [I] [Improvement] Avoid using known ports for playgournd docker containers [gravitino-playground]

2025-01-14 Thread via GitHub


shaofengshi closed issue #60: [Improvement] Avoid using known ports for 
playgournd docker containers
URL: https://github.com/apache/gravitino-playground/issues/60


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Improvement] Avoid using known ports for playgournd docker containers [gravitino-playground]

2024-08-19 Thread via GitHub


jerqi commented on issue #60:
URL: 
https://github.com/apache/gravitino-playground/issues/60#issuecomment-2296074137

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


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] [Improvement] Avoid using known ports for playgournd docker containers [gravitino-playground]

2024-08-16 Thread via GitHub


FANNG1 commented on issue #60:
URL: 
https://github.com/apache/gravitino-playground/issues/60#issuecomment-2293428374

   +1


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



[I] [Improvement] Avoid using known ports for playgournd docker containers [gravitino-playground]

2024-08-16 Thread via GitHub


shaofengshi opened a new issue, #60:
URL: https://github.com/apache/gravitino-playground/issues/60

   - 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, , 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, such as the following:
   
   
![image](https://github.com/user-attachments/assets/71877f97-58c4-469f-9006-dcf6e497614c)

   
   - 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,,4040,8080,8090,9001,9000,9083,50070
 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]