Add workaround for port conflicts #508
Conversation
|
I've added this to the FAQ as we ought to discuss whether we want a Troubleshooting section under Using Appsody, and if so whether FAQ would then be redundant... |
There was a problem hiding this comment.
I think a troubleshooting section would be a good idea. We'd have to see what other FAQ items could be moved here or elsewhere in order to eliminate it. I've not been a fan, so would be a positive move IMO. Approving anyway so this can go in ahead of any other work.
content/docs/faq.md
Outdated
| @@ -67,3 +67,18 @@ Here is a list of commands that are part of the standard Appsody flow of work, w | |||
| ``` | |||
| export APPSODY_PULL_POLICY=IFNOTPRESENT | |||
| ``` | |||
|
|
|||
| ### 7. Why does my Open Liberty Appsody project on macOS fail with the error “address already in use”? | |||
There was a problem hiding this comment.
I think this is specific to a port 9443 on macOS and not specific to a stack? Should we just say Appsody project rather than calling our Open Liberty?
There was a problem hiding this comment.
At the current time we're only seeing this with the Open Liberty and Microprofile stacks, as they are both using port 9443, this could happen with other stacks if they also use 9443. However, I'll change it as requested.
Checklist
Description
Added a new FAQ to address the associated issue.
Related Issues
Fixes #505