-
Notifications
You must be signed in to change notification settings - Fork 54
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
Use proper init process #3
Comments
Having seen this problem in our environment, I'm putting together a fix for this. It is based on top of my fix for #4, so I need/want to wait to see what happens to it before I push this one. |
Is there any progress on this ticket? I don't know why he didn't create a PR. @cptactionhank will it be possible to merge this changeset into your project? |
@cguentherTUChemnitz I created a PR and withdrew it again as the "proper init process" is already part of docker and docker-compose since 1.13.0: see comment here #7 |
We are having a lot of zombie processes in our process list:
(continues for 1000s of lines).
The SSH processes are most probably created by Bamboo when it fetches Git repositories from Bitbucket.
This issue is probably related to the fact that Java is the main process in the docker container, and could easily be solved by using tini or dumb-init in the entrypoint script.
The text was updated successfully, but these errors were encountered: