Skip to main content

Troubleshooting

If you get the Port already in use exception when starting an alternate container, recheck that there is not already a container running using the default parameters.

If you are still getting the error, it may also be that the port is actually in use by an unrelated process, so change the ports in the configuration adaption scripts and rerun these to apply the changes.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!