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
Kernel panic (3.16) on debian jessie when running docker containers with healthchecks #30402
Comments
Do you have the full kernel stack trace? |
Can you try running Debian unstable or testing instead? The kernel in stable is pretty old, and the new Debian which will be out in a few months should be a lot better. |
Sure, I could try to reproduce on The problem with https://docs.docker.com/engine/installation/linux/debian/
|
I didn't manage to reproduce this on the following environments
It seems that kernel bug is exposed on |
I've had the same issues on a Debian Jessie box when using health checks:
I upgraded my kernel but I also removed health checks temporarily because I didn't have easy access to reboot the box so I am not certain if upgrading the kernel fixed it. |
+1 I try a lot of things (sleep in healthcheck, static binary,...) same issue, I dump same oops kernel issue (few seconds before oops, it's seems cpu load increase a lot)... only one way to come back to a normal state... not use it... however it's seems with specific config like : the oops seems appear less often |
I there anything actionable here? Or is this a kernel bug? Debian 9 "stretch" is currently in "full freeze" (https://wiki.debian.org/DebianStretch) and hopefully available as "stable" soon. |
You can upgrade to currently kernel 4.9 from jessie-backports. We are currently facing this exact situation, and doing a kernel-only upgrade. |
@gyorgyabraham Unfortunately the kernel 4.9 from jessie backports doesn't include btrfs so the user has to save and migrates his images before upgrading. |
@unixfox yeah and 4.9 lacks aufs too. So manual storage migration is necessary. |
I can confirm this bug still occurs. Once we removed healthcheck definitions from Dockerfiles the problem disappeared. |
Thanks for the info. I compiled 4.9 kernel with aufs patch, and it completely resolved the issue.
2017. szeptember 9. 19:09:56 CEST, Spectrik <notifications@github.com> írta:
…I can confirm this bug still occurs. Once we removed healthcheck
definitions from Dockerfiles the problem disappeared.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#30402 (comment)
--
Ezt a levelet az Android készülékemről küldtem K-9 Mail-el. Elnézést a tömörségemért.
|
3.16.0-4-amd64 #1 SMP Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux
|
@EccoB if you check my old comment (6 Feb 2017) I recommend you to increase container health check interval, this seems limit panic appearance (or upgrade kernel if possible) |
Just upgrade the kernel or the whole distro. :)
|
I have this issue as well running just two Docker containers on Debian Jessie with kernel |
Jessie is no longer supported: docker/docker-ce-packaging#253 If somebody is still hitting this, please ask the distro's kernel maintainers. |
BUG REPORT INFORMATION
Description
Kernel panic (3.16) on debian jessie when running docker containers with healthchecks.
Steps to reproduce the issue:
apt update
and installdocker
following the official instructions.solr:alpine
image and build a new one with healthchecks using aDockerfile
.Describe the results you received:
kernel panic, server crashes.
Describe the results you expected:
no crash
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
I was able to reproduce with both
1.12.5
and1.13.0
docker versions on physical servers and VirtualBox VMs, all runningjessie
with1.16
kernel. Kernel Panic screenshots are available.I was able to reproduce with
1m
healthcheck intervals as well.CPU/RAM
systemd config (running on Debug mode with private registry enabled)
Dockerfile and image build
deployment of 25 containers
kern.log
logjournalctl docker.service
logThe text was updated successfully, but these errors were encountered: