-
Notifications
You must be signed in to change notification settings - Fork 120
java-openliberty: appsody run
fails if Kubernetes is enabled
#652
Comments
This was raised in Slack at the end of last week and is going into the FAQ on Please do comment on the FAQ I've written as I've described the workaround where we change the port, but not the workaround of shutting down Kubernetes. Once this is merged my thoughts are that we should link to it from the Java microprofile and Open Liberty stack readmes with wording such as “Note: If you find that your Open Liberty Appsody project on macOS fails with the error “address already in use”, see the [Appsody FAQs](link to details on website).” |
The workaround sounds OK, but this issue should stay open for fixing the underlying problem in the stack, yeah? |
@scottkurz What are your thoughts on this? In the past, we have tried to use the ports that the users of the language/framework are most familiar with so the developer's find transition to Appsody easier, but in this case this is causing more work than we want. We could always use |
@neeraj-laad in asking me my thoughts, I feel like you understand a piece of this that I'm missing. E.g. why does the fact that k8s is active matter? Maybe we could chat on Slack? |
Describe the bug
On macOS, using Docker Desktop's built-in Kubernetes, the default template does not run if Kubernetes is enabled.
To Reproduce
Steps to reproduce the behavior:
mkdir testapp && cd testapp
appsody init java-openliberty
appsody run
Expected behavior
The default app starts.
Actual behaviour
The app does not start.
If I then shut down Kubernetes on my machine, it works:
Environment Details (please complete the following information):
macOS 10.15.2 Catalina
Docker Desktop 2.2.0.0 stable with Kubernetes v1.15.5
Appsody CLI 0.5.8
If applicable please specify:
The text was updated successfully, but these errors were encountered: