-
Notifications
You must be signed in to change notification settings - Fork 5
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
WIP: Bedrock server #23
Conversation
Signed-off-by: Christoph Görn <[email protected]>
Signed-off-by: Christoph Görn <[email protected]>
Signed-off-by: Christoph Görn <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
itzg/docker-minecraft-bedrock-server#6
Can you configure the port in the config file?
After it's being created. Which might be a chicken egg problem
Christoph Görn ***@***.***> schrieb am So. 2. Mai 2021 um
08:37:
… @tumido <https://github.com/tumido> @durandom
<https://github.com/durandom> looks like OCP doesnt like to use the
Bedrock port, any idea how to fix it?
The Service "minecraft-server-creative" is invalid:
spec.ports[0].nodePort: Invalid value: 19132: provided port is not in the
valid range. The range of valid ports is 30000-32767
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABHQYA64LH5DNNNB6UFIUDTLTXLFANCNFSM437CW5PQ>
.
|
uhh.. I was under the impression that the bedrock client needs this specific port, let's test with .... |
Signed-off-by: Christoph Görn <[email protected]>
Signed-off-by: Christoph Görn <[email protected]>
Signed-off-by: Christoph Görn <[email protected]>
Signed-off-by: Christoph Görn <[email protected]>
@goern the node port range is fixed and I don't think we can do much about it. The range is controlled via |
Like.. in the end it's patching a single config resource, but it supports only a single range definition + may cause firewall troubles... 🤷 |
closes #20