{"action":"opened","issue":{"url":"https://api.github.com/repos/wercker/support/issues/128","labels_url":"https://api.github.com/repos/wercker/support/issues/128/labels{/name}","comments_url":"https://api.github.com/repos/wercker/support/issues/128/comments","events_url":"https://api.github.com/repos/wercker/support/issues/128/events","html_url":"https://github.com/wercker/support/issues/128","id":106007940,"number":128,"title":"Random failing builds because of issues with linked docker ElasticSearch service","user":{"login":"timflapper","id":319370,"avatar_url":"https://avatars.githubusercontent.com/u/319370?v=3","gravatar_id":"","url":"https://api.github.com/users/timflapper","html_url":"https://github.com/timflapper","followers_url":"https://api.github.com/users/timflapper/followers","following_url":"https://api.github.com/users/timflapper/following{/other_user}","gists_url":"https://api.github.com/users/timflapper/gists{/gist_id}","starred_url":"https://api.github.com/users/timflapper/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/timflapper/subscriptions","organizations_url":"https://api.github.com/users/timflapper/orgs","repos_url":"https://api.github.com/users/timflapper/repos","events_url":"https://api.github.com/users/timflapper/events{/privacy}","received_events_url":"https://api.github.com/users/timflapper/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-11T13:12:15Z","updated_at":"2015-09-11T13:12:15Z","closed_at":null,"body":"Our builds are using three different linked docker containers for external services: Postgres, Redis and ElasticSearch. Most of our builds run without a hitch but some of our builds are showing random ElasticSearch errors. We haven't been able to reproduce it locally. Because I can't look inside the ElasticSearch container to see what's happening there it all comes down to guess work what might be happening. \r\n\r\nWe had this problem earlier this week then it went away for a couple of days and today it happened again. This makes me think it might be due to some insufficient server resource like memory or disk space which makes ElasticSearch misbehave.\r\n\r\nI know it's a vague description but unfortunately that's all I can offer. Hopefully you can help us out."}}