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
Docker out of file descriptors/processes #19124
Comments
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information. For more information about reporting issues, see CONTRIBUTING.md. You don't have to include this information if this is a feature request (This is an automated, informational response) BUG REPORT INFORMATIONUse the commands below to provide key information from your environment:
Provide additional environment details (AWS, VirtualBox, physical, etc.): List the steps to reproduce the issue: Describe the results you received: Describe the results you expected: Provide additional info you think is important: ----------END REPORT --------- #ENEEDMOREINFO |
ulimits in your shell are not the same as ulimits set by the init system. |
I was running into this problem recently as well. Whether it's related or not, this bug report's workaround worked for me: https://bugs.archlinux.org/task/47303 That is, add |
@BurntSushi That fixed the problem, thanks. This looks like it's a problem (or change?) with Linux containers, so probably of no further relevance here. |
Thanks @BurntSushi wow that was hard to trackdown. Well done. |
Note that we're updating the docker.service for docker 1.10 to override the default value; #19391 |
Docker (or postgresql, or i'm not really sure...) seems to be running out of resources,
docker exec -it <id> bash
is also track tracing (on any container)These errors happen both within the container and in the host, dispute seemingly plenty of memory to spare...
At first i thought this was an issue with postgresql, however frequently
docker exec -it <id> bash
will simply return (without an error as far as i know) anddocker inspect <id>
will return 404's, and then all my containers seem to be killedI'm not too familiar with docker, but the limits don't seem to match up with what I would expect (the container having lower limits than the host)...
container:
host:
docker info:
docker version:
docker inspect on the postgresql container
I'm running Arch Linux
Linux ARCHY 4.3.3-2-ARCH #1 SMP PREEMPT Wed Dec 23 20:09:18 CET 2015 x86_64 GNU/Linux
and pre-4.3.3 kernel update things were working fine in docker. I've rebuild all the containers since then. These were the packaged updated between it working, and nowThanks,
Nic
The text was updated successfully, but these errors were encountered: