[GH-ISSUE #186] Seriviceapi Error while docker-compose up #181

New issue

Closed

opened 2026-02-27 15:55:31 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 15:55:31 +03:00

Owner

Originally created by @tushar21 on GitHub (Aug 26, 2018).
Original GitHub issue: https://github.com/RD17/ambar/issues/186

I am having error while docker compose up : ERROR: for serviceapi Container "e6a3e3b4cef9" is unhealthy.

Originally created by @tushar21 on GitHub (Aug 26, 2018). Original GitHub issue: https://github.com/RD17/ambar/issues/186 I am having error while docker compose up : ERROR: for serviceapi Container "e6a3e3b4cef9" is unhealthy.

kerem closed this issue

2026-02-27 15:55:31 +03:00

kerem commented

2026-02-27 15:55:31 +03:00

Author

Owner

@steve-boyle commented on GitHub (Aug 27, 2018):

I would say, run sudo docker ps to get the instance name for the serviceapi container. The name is going to be something like username_serviceapi_1.
Then run sudo docker logs username_serviceapi_1, obviously you want to use your proper instance name there. Hopefully, you can figure out your issue from the log.

@steve-boyle commented on GitHub (Aug 27, 2018): I would say, run `sudo docker ps` to get the instance name for the serviceapi container. The name is going to be something like username_serviceapi_1. Then run `sudo docker logs username_serviceapi_1`, obviously you want to use your proper instance name there. Hopefully, you can figure out your issue from the log.

kerem commented

2026-02-27 15:55:31 +03:00

Author

Owner

@tushar21 commented on GitHub (Aug 31, 2018):

I can't find the root cause but got the temporary solution. After clearing the datastore, serviceapi is working again.

@tushar21 commented on GitHub (Aug 31, 2018): I can't find the root cause but got the temporary solution. After clearing the datastore, serviceapi is working again.