Pass ulimit to dockerd
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm new in kubernetes and I'm trying to deploy an elasticsearch on it.
Currently, I have a problem with the number of file descriptor required by elasticsearch and allow by docker.
[1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
So to fix that I have tried 3 different ways:
way 1
From the docker documentation, dockerd should use the system value as default value.
- set
/etc/security/limits.con
f with* - nofile 65536
- reboot
- execute
ulimit -Hn && ulimit -Sn
return return 65536 twice - execute
docker run --rm centos:7 /bin/bash -c 'ulimit -Hn && ulimit -Sn'
(should return 65536 twice but no, return 4096 and 1024 )
way 2
- add
--default-ulimit nofile=65536:65536
to/var/snap/microk8s/current/args/dockerd
- reboot
- execute
docker run --rm centos:7 /bin/bash -c 'ulimit -Hn && ulimit -Sn'
(should return 65536 twice but no return 4096 and 1024)
way 3
add
"default-ulimit" : {
"nofile":{
"Name":" nofile",
"Hard":" 65536",
"Soft":" 65536"
}
}
to
/var/snap/microk8s/354/args/docker-daemon.json
- execute
systemctl restart snap.microk8s.daemon-docker.service
- execute
journalctl -u snap.microk8s.daemon-docker.service -f
will returnunable to configure the Docker daemon with file /var/snap/microk8s/354/args/docker-daemon.json: the following directives don't match any configuration option: nofile
The only way I found for set the ulimit is to pass --ulimit nofile=65536:65536
to the docker run command. But I cannot do that inside my kubernetes statesfullset config.
So do you know how I can solve this problem ?
I didn't somethings wrong here ?
Thanks in advance for your help
ps: I'm on ubuntu 18.0.1 with docker 18.06.1-ce and microk8s installed with snap
docker elasticsearch kubernetes ulimit
add a comment |
I'm new in kubernetes and I'm trying to deploy an elasticsearch on it.
Currently, I have a problem with the number of file descriptor required by elasticsearch and allow by docker.
[1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
So to fix that I have tried 3 different ways:
way 1
From the docker documentation, dockerd should use the system value as default value.
- set
/etc/security/limits.con
f with* - nofile 65536
- reboot
- execute
ulimit -Hn && ulimit -Sn
return return 65536 twice - execute
docker run --rm centos:7 /bin/bash -c 'ulimit -Hn && ulimit -Sn'
(should return 65536 twice but no, return 4096 and 1024 )
way 2
- add
--default-ulimit nofile=65536:65536
to/var/snap/microk8s/current/args/dockerd
- reboot
- execute
docker run --rm centos:7 /bin/bash -c 'ulimit -Hn && ulimit -Sn'
(should return 65536 twice but no return 4096 and 1024)
way 3
add
"default-ulimit" : {
"nofile":{
"Name":" nofile",
"Hard":" 65536",
"Soft":" 65536"
}
}
to
/var/snap/microk8s/354/args/docker-daemon.json
- execute
systemctl restart snap.microk8s.daemon-docker.service
- execute
journalctl -u snap.microk8s.daemon-docker.service -f
will returnunable to configure the Docker daemon with file /var/snap/microk8s/354/args/docker-daemon.json: the following directives don't match any configuration option: nofile
The only way I found for set the ulimit is to pass --ulimit nofile=65536:65536
to the docker run command. But I cannot do that inside my kubernetes statesfullset config.
So do you know how I can solve this problem ?
I didn't somethings wrong here ?
Thanks in advance for your help
ps: I'm on ubuntu 18.0.1 with docker 18.06.1-ce and microk8s installed with snap
docker elasticsearch kubernetes ulimit
aren't you using ELK images? I thought they had correct ulimit already
– Mysterion
Jan 4 at 11:47
Yes, I have tried withdocker.elastic.co/elasticsearch/elasticsearch-oss:6.5.4
and also with helm chart from elastic and the official one. And with all of them I have the same trouble....
– David
Jan 4 at 13:32
add a comment |
I'm new in kubernetes and I'm trying to deploy an elasticsearch on it.
Currently, I have a problem with the number of file descriptor required by elasticsearch and allow by docker.
[1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
So to fix that I have tried 3 different ways:
way 1
From the docker documentation, dockerd should use the system value as default value.
- set
/etc/security/limits.con
f with* - nofile 65536
- reboot
- execute
ulimit -Hn && ulimit -Sn
return return 65536 twice - execute
docker run --rm centos:7 /bin/bash -c 'ulimit -Hn && ulimit -Sn'
(should return 65536 twice but no, return 4096 and 1024 )
way 2
- add
--default-ulimit nofile=65536:65536
to/var/snap/microk8s/current/args/dockerd
- reboot
- execute
docker run --rm centos:7 /bin/bash -c 'ulimit -Hn && ulimit -Sn'
(should return 65536 twice but no return 4096 and 1024)
way 3
add
"default-ulimit" : {
"nofile":{
"Name":" nofile",
"Hard":" 65536",
"Soft":" 65536"
}
}
to
/var/snap/microk8s/354/args/docker-daemon.json
- execute
systemctl restart snap.microk8s.daemon-docker.service
- execute
journalctl -u snap.microk8s.daemon-docker.service -f
will returnunable to configure the Docker daemon with file /var/snap/microk8s/354/args/docker-daemon.json: the following directives don't match any configuration option: nofile
The only way I found for set the ulimit is to pass --ulimit nofile=65536:65536
to the docker run command. But I cannot do that inside my kubernetes statesfullset config.
So do you know how I can solve this problem ?
I didn't somethings wrong here ?
Thanks in advance for your help
ps: I'm on ubuntu 18.0.1 with docker 18.06.1-ce and microk8s installed with snap
docker elasticsearch kubernetes ulimit
I'm new in kubernetes and I'm trying to deploy an elasticsearch on it.
Currently, I have a problem with the number of file descriptor required by elasticsearch and allow by docker.
[1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
So to fix that I have tried 3 different ways:
way 1
From the docker documentation, dockerd should use the system value as default value.
- set
/etc/security/limits.con
f with* - nofile 65536
- reboot
- execute
ulimit -Hn && ulimit -Sn
return return 65536 twice - execute
docker run --rm centos:7 /bin/bash -c 'ulimit -Hn && ulimit -Sn'
(should return 65536 twice but no, return 4096 and 1024 )
way 2
- add
--default-ulimit nofile=65536:65536
to/var/snap/microk8s/current/args/dockerd
- reboot
- execute
docker run --rm centos:7 /bin/bash -c 'ulimit -Hn && ulimit -Sn'
(should return 65536 twice but no return 4096 and 1024)
way 3
add
"default-ulimit" : {
"nofile":{
"Name":" nofile",
"Hard":" 65536",
"Soft":" 65536"
}
}
to
/var/snap/microk8s/354/args/docker-daemon.json
- execute
systemctl restart snap.microk8s.daemon-docker.service
- execute
journalctl -u snap.microk8s.daemon-docker.service -f
will returnunable to configure the Docker daemon with file /var/snap/microk8s/354/args/docker-daemon.json: the following directives don't match any configuration option: nofile
The only way I found for set the ulimit is to pass --ulimit nofile=65536:65536
to the docker run command. But I cannot do that inside my kubernetes statesfullset config.
So do you know how I can solve this problem ?
I didn't somethings wrong here ?
Thanks in advance for your help
ps: I'm on ubuntu 18.0.1 with docker 18.06.1-ce and microk8s installed with snap
docker elasticsearch kubernetes ulimit
docker elasticsearch kubernetes ulimit
asked Jan 4 at 10:40
DavidDavid
209316
209316
aren't you using ELK images? I thought they had correct ulimit already
– Mysterion
Jan 4 at 11:47
Yes, I have tried withdocker.elastic.co/elasticsearch/elasticsearch-oss:6.5.4
and also with helm chart from elastic and the official one. And with all of them I have the same trouble....
– David
Jan 4 at 13:32
add a comment |
aren't you using ELK images? I thought they had correct ulimit already
– Mysterion
Jan 4 at 11:47
Yes, I have tried withdocker.elastic.co/elasticsearch/elasticsearch-oss:6.5.4
and also with helm chart from elastic and the official one. And with all of them I have the same trouble....
– David
Jan 4 at 13:32
aren't you using ELK images? I thought they had correct ulimit already
– Mysterion
Jan 4 at 11:47
aren't you using ELK images? I thought they had correct ulimit already
– Mysterion
Jan 4 at 11:47
Yes, I have tried with
docker.elastic.co/elasticsearch/elasticsearch-oss:6.5.4
and also with helm chart from elastic and the official one. And with all of them I have the same trouble....– David
Jan 4 at 13:32
Yes, I have tried with
docker.elastic.co/elasticsearch/elasticsearch-oss:6.5.4
and also with helm chart from elastic and the official one. And with all of them I have the same trouble....– David
Jan 4 at 13:32
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54037329%2fpass-ulimit-to-dockerd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54037329%2fpass-ulimit-to-dockerd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
aren't you using ELK images? I thought they had correct ulimit already
– Mysterion
Jan 4 at 11:47
Yes, I have tried with
docker.elastic.co/elasticsearch/elasticsearch-oss:6.5.4
and also with helm chart from elastic and the official one. And with all of them I have the same trouble....– David
Jan 4 at 13:32