-
Notifications
You must be signed in to change notification settings - Fork 129
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
Error when starting docker #56
Comments
Hi @sagyHarpaz |
I always got this message |
@sagyHarpaz can you see if the You can also use the Also, assuming there's something wrong with the container, use |
When I ran docker ps command I got: |
@sagyHarpaz did you check the Docker Desktop's sharing option? Check |
Can you check what is your Docker Desktop version? In the past, we experienced issues with specific versions. In any case, I suggest trying to update to the latest version and try again 🙂 |
I already have the latest version 2.3.0.4 (46911) |
OK, this might be a volume issue, try the following: Edit the docker-compose file, change the services:
...
mongo:
volumes:
- mongodata:/data/db
- c:/opt/trains/data/mongo/configdb:/data/configdb
...
volumes:
mongodata: Then do: docker-compose down
docker volume create --name=mongodata
docker-compose up BTW - seems like a known mongo issue on Windows: docker-library/mongo#385 |
now I get this error |
Hi @sagyHarpaz, can you please share the logs from trains-elastic and trains-apiserver dockers? I suspect that we will see some errors there. |
Hi when I tried to run "docker-compose -f docker-compose-win10.yml up"
I got:
Unexpected API error for trains-redis (HTTP code 502)
Response body:
Bad response from Docker engine
Unexpected API error for trains-webserver (HTTP code 502)
Response body:
Bad response from Docker engine
Unexpected API error for trains-elastic (HTTP code 502)
Response body:
Bad response from Docker engine
Unexpected API error for trains-apiserver (HTTP code 502)
Response body:
Bad response from Docker engine
Unexpected API error for trains-fileserver (HTTP code 502)
Response body:
Bad response from Docker engine
The text was updated successfully, but these errors were encountered: