[GH-ISSUE #289] Unhealthy containers #272

New issue

Closed

opened 2026-02-27 15:55:54 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @cogicero on GitHub (Aug 5, 2020).
Original GitHub issue: https://github.com/RD17/ambar/issues/289

While troubleshooting this issue https://github.com/RD17/ambar/issues/288 I shut down Docker and tried to start it up again, only to get the error message that the containers are unhealthy. I didn't make any changes to the system!

ERROR: for pipeline0  Container "aca961201dc1" is unhealthy.

ERROR: for crawler  Container "aca961201dc1" is unhealthy.

ERROR: for webapi  Container "aca961201dc1" is unhealthy.
ERROR: Encountered errors while bringing up the project.

The other containers are running fine.

Trying to fix this now, and following hints I have seen here, I have tried assigning 6GB of RAM to ES, and I also set sudo sysctl -w vm.max_map_count=4194304. Any ideas what is wrong here please?

Originally created by @cogicero on GitHub (Aug 5, 2020). Original GitHub issue: https://github.com/RD17/ambar/issues/289 While troubleshooting this issue [https://github.com/RD17/ambar/issues/288](url) I shut down Docker and tried to start it up again, only to get the error message that the containers are unhealthy. I didn't make any changes to the system! ``` ERROR: for pipeline0 Container "aca961201dc1" is unhealthy. ERROR: for crawler Container "aca961201dc1" is unhealthy. ERROR: for webapi Container "aca961201dc1" is unhealthy. ERROR: Encountered errors while bringing up the project. ``` The other containers are running fine. Trying to fix this now, and following hints I have seen here, I have tried assigning 6GB of RAM to ES, and I also set sudo sysctl -w vm.max_map_count=4194304. Any ideas what is wrong here please?

kerem

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

closed this issue
added the
wontfix
label

kerem commented

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

Author

Owner

@stale[bot] commented on GitHub (Aug 22, 2020):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Aug 22, 2020): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.