-
Notifications
You must be signed in to change notification settings - Fork 7
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
Install via docker-compose does not work because of ports conflicts #22
Comments
ok seems related to the conflict with already used ports:
|
Ok, installation is now in progress (after that i ensured that i have no other container running on the same ports, i had the issue because is use the same docker-compose.yml for my standard but this can happen with any container exposing on the port 8080 which is super common). We have several option there,
|
Once installed i'd like to know where i can access my pim, for instance: "your pim is now available on http://localhost:8080/" |
I can't access to the PIM in my browser at the end, i got a 500 error:
Don't hesitate if you need any further information or need a docker beta tester and good luck to continue to improve this tool 💪 ❤️ |
Yes, I've already seen the problem with docker when port are already used, by using unexpected port it might be easier, you right. It is normal you can't access the PIM I think as we don't have install assets or javascript dependencies |
Thanks a lot for the report :) |
I tested with docker-compose already running for other projects (the pim i try to migrate)
I think it has conflict with other containers using the same port, main issue here for me is to not have the docker output, i can't easily debug it. I'm doing extra tests and keep you updated.
The text was updated successfully, but these errors were encountered: