-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Too many open files with codenvy/che:nightly
#143
Comments
codenvy/che;nightly
codenvy/che;nightly
codenvy/che:nightly
2015-12-29 06:10:56,487[ost-startStop-1] [WARN ] [.c.p.d.c.DockerRegistryChecker 50] - Docker registry http://localhost:5000 is not available, which means that you won't be able to save snapshots of your workspaces. |
@wu560130911 Not understand why you quote this warning? It should not related to the "too many open files" issue |
I periodically run into this issue, but have been unable to cause it to happen reliably. In doing research on it, there are some additional fixes. On the host system:
Also, though I believe it is unrelated, you will need to start Che with --privileged mode. I am going to spend some time this afternoon attempting to reliably recreate the too many open files circumstances so that we can put some tests around it and also explore different solutions. |
@TylerJewell Thanks very much, I will try it tomorrow ~ |
Sure thing. It should be noted that running Che inside of a Docker
But we wnat to make this work, so I also think it's a great test case & Tyler Jewell | CEO | tyler@codenvy.com | 978.884.5355 On Tue, Dec 29, 2015 at 1:02 PM, freewind [email protected] wrote:
|
You do not run the image in the right way. --privileged flag is Mandatory for Docker to start inside a Docker container. Please, check docs - https://eclipse-che.readme.io/v4.0/docs/install-using-docker |
@eivantsov Yes, you right right!! Sorry for my stupid mistake. But the error is too misleading 😭 |
We have been working on a new set of che startup scripts that will start This will prevent these sorts of startup mistakes from happening. If you want to test it, you can check out branch IDEX-3975. The che.bat These scripts also take care to start virtualbox, docker-machine, and Tyler Jewell | CEO | tyler@codenvy.com | 978.884.5355 On Wed, Dec 30, 2015 at 6:56 PM, freewind [email protected] wrote:
|
@TylerJewell Thanks, that's great! I will try it later, these scripts are really helpful for docker newbies |
@eivantsov Sometimes the "too many open files" error still appear even if I set |
Sometimes? Under what conditions? |
@eivantsov It didn't happen today. "Sometimes" means I didn't change anything, only restart the container with the same command, it reported that error, but I can't remember the details. I will reopen this next time I see it |
It is suddenly report "too many open files". I didn't do anything special, just kill previous container and run it again (it was OK last time). The command is:
The log is:
I can't see if is the memory run up, because no matter I input any command, it show the same error:
|
I just tried it on freshly created machines on Digital Ocean and Azure, and failed to reproduce it. -bash: start_pipeline: pgrp pipe: Too many open files in system - is this on your host or in a container? Can you exec into a container after it has been started and run docker info there? |
It's from the log of the docker container which runs the che.
Sorry, when I see that errors, I can't do anything on the host. Even a simple I have to kill the container by press "ctrl + c", and then I can execute other linux commands Maybe I can record it next time and share to you |
It is a host problem then. I have tried to reproduce it on different environments - no luck. It is possible that when a container starts it consumes hosts resources that may be insufficient. |
Just now, it happens one time again. But if I
And we have enough resources this time:
Seems it happens quite randomly. It has never happened in my mac + virtual box, but happened in digital-ocean and another could host managed by our company. |
Just checked it with Digital Ocean - Che started just fine. The issue is with starting Docker in Docker - it looks like this does not work well in all environments. |
@freewind can you still repeatedly reproduce this issue? Only with Digital Ocean or locally as well? |
@freewind I think after switching to a a no-docker-in-docker image the problem fixed itself. Closing the issue since we do not start Docker in Docker anymore. |
I have the same problem with this issue #140.
I run the image
codenvy/che:nightly
in a virtual box, which is running ubuntu 14.04, and the "open files" settings is increased as following:and append the following to
/etc/security/limits.conf
:Then I start
codenvy/che:nightly
:It seems started correctly:
But now I can't run any commands, even the simplest
ls
:Then I visit the che from browser:
It doesn't show anything, instead, I can see many "Too many open files in system" showing on the log:
I tried to
docker ps
but failed:The text was updated successfully, but these errors were encountered: