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
Bump watchdog for GC optimisation #115
Comments
Derek add label: help wanted |
hi @martindekov i got this.
|
alexellis
changed the title
Bump watchdog with memory leak issue fix
Bump watchdog for GC optimisation
Jan 12, 2019
Hello @roncrivera I approved your PR nice work ! |
Derek close: PR merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PR 1001 in the faas repo fixed a GC optimisation in the watchdog, but currently images are with older watchdog binary
Expected Behaviour
Pull watchdog binary with latest release (
0.9.14
)Current Behaviour
Most of the templates are still with
0.9.6
release of the watchdog with the unoptimised GCPossible Solution
In the templates which are using the classic watchdog change the
Dockerfile
to pull latest watchdog binary(0.9.14
) here is example PR which updates the watchdog.Steps to Reproduce (for bugs)
N.A. People use watchdog binary with memory leak unless they manually update their dockerfiles.
Context
The binary which is used now (
0.9.6
) for the Dockerfiles needs updating to the latest.The text was updated successfully, but these errors were encountered: