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;
}







0















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.




  1. set /etc/security/limits.conf with * - nofile 65536

  2. reboot

  3. execute ulimit -Hn && ulimit -Sn return return 65536 twice

  4. 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




  1. add --default-ulimit nofile=65536:65536 to /var/snap/microk8s/current/args/dockerd

  2. reboot

  3. 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





  1. add



    "default-ulimit" : {
    "nofile":{
    "Name":" nofile",
    "Hard":" 65536",
    "Soft":" 65536"
    }
    }



    to /var/snap/microk8s/354/args/docker-daemon.json



  2. execute systemctl restart snap.microk8s.daemon-docker.service

  3. execute journalctl -u snap.microk8s.daemon-docker.service -f will return unable 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







share|improve this question























  • 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


















0















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.




  1. set /etc/security/limits.conf with * - nofile 65536

  2. reboot

  3. execute ulimit -Hn && ulimit -Sn return return 65536 twice

  4. 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




  1. add --default-ulimit nofile=65536:65536 to /var/snap/microk8s/current/args/dockerd

  2. reboot

  3. 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





  1. add



    "default-ulimit" : {
    "nofile":{
    "Name":" nofile",
    "Hard":" 65536",
    "Soft":" 65536"
    }
    }



    to /var/snap/microk8s/354/args/docker-daemon.json



  2. execute systemctl restart snap.microk8s.daemon-docker.service

  3. execute journalctl -u snap.microk8s.daemon-docker.service -f will return unable 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







share|improve this question























  • 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














0












0








0








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.




  1. set /etc/security/limits.conf with * - nofile 65536

  2. reboot

  3. execute ulimit -Hn && ulimit -Sn return return 65536 twice

  4. 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




  1. add --default-ulimit nofile=65536:65536 to /var/snap/microk8s/current/args/dockerd

  2. reboot

  3. 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





  1. add



    "default-ulimit" : {
    "nofile":{
    "Name":" nofile",
    "Hard":" 65536",
    "Soft":" 65536"
    }
    }



    to /var/snap/microk8s/354/args/docker-daemon.json



  2. execute systemctl restart snap.microk8s.daemon-docker.service

  3. execute journalctl -u snap.microk8s.daemon-docker.service -f will return unable 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







share|improve this question














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.




  1. set /etc/security/limits.conf with * - nofile 65536

  2. reboot

  3. execute ulimit -Hn && ulimit -Sn return return 65536 twice

  4. 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




  1. add --default-ulimit nofile=65536:65536 to /var/snap/microk8s/current/args/dockerd

  2. reboot

  3. 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





  1. add



    "default-ulimit" : {
    "nofile":{
    "Name":" nofile",
    "Hard":" 65536",
    "Soft":" 65536"
    }
    }



    to /var/snap/microk8s/354/args/docker-daemon.json



  2. execute systemctl restart snap.microk8s.daemon-docker.service

  3. execute journalctl -u snap.microk8s.daemon-docker.service -f will return unable 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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










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 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



















  • 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

















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












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
});


}
});














draft saved

draft discarded


















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
















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







-

Popular posts from this blog

Monofisismo

Image
Monofisismo (do grego: monos - "único, singular" e physis - "natureza") é o ponto de vista cristológico que defende que, depois da união do divino e do humano na encarnação histórica, Jesus Cristo, como encarnação do Filho ou Verbo ( Logos ) de Deus, teria apenas uma única "natureza", a divina, e não uma síntese de ambas. O monofisismo é contraposto pelo diofisismo (ou "diafisismo"), que defende que Jesus preservou em si as duas naturezas. Historicamente, o monofisismo se refere primordialmente à posição dos que (especialmente no Egito e, em menor grau, na Síria) rejeitaram as decisões do Concílio de Calcedônia em 451 (o quarto concílio ecumênico). Os membros mais moderados entre eles, porém, defendem a teologia "miafisita", que se tornou a oficial para as Igrejas Ortodoxas Orientais. Muitos ortodoxos orientais, porém, rejeitam essa classificação, mesmo como um termo genérico, mas ele é amplamente utilizado na literatura históri
Read more

Angular Downloading a file using contenturl with Basic Authentication

Image
0 I have a contentUrl when user clicks on that,file should be downloaded. If I try to browse the contentUrl in the browser it asks for Userid and password.I believe this is Basic Authentication.I dont want user to enter UserId and Password so I am passing it Authorization(Please see below code). Url looks some thing like this: http://XXX.XXX.XX.XXX:8080/flowable-rest/service/runtime/tasks/90875/attachments/90555/content let username : string = 'admin'; let pwd : string = 'test'; let headers = new Headers(); headers.set('Accept', 'text/json'); headers.append('Content-Type', 'application/json'); headers.set('Access-Control-Allow-Origin', '*'); headers.set('Access-Control-Allow-Methods','POST, GET, OPTIONS, PUT, DELETE'); head
Read more

Olmecas

Image
Monumento 1, uma das quatro cabeças colossais encontradas em La Venta, com altura aproximada de 3 metros Olmecas é a designação do povo e da civilização que estiveram na origem da antiga cultura pré-colombiana da Mesoamérica e que se desenvolveram nas regiões tropicais do centro-sul do atual México durante o pré-clássico, próximo de onde hoje estão localizados os estados mexicanos de Veracruz e Tabasco, no Istmo de Tehuantepec, numa zona designada área nuclear olmeca. A cultura olmeca floresceu nesta região aproximadamente entre 1500 e 400 a.C., [ 1 ] e crê-se que tenha sido a civilização-mãe de todas as civilizações mesoamericanas que se desenvolveram posteriormente. [ 2 ] No entanto, desconhece-se a sua exacta filiação étnica, ainda que existam numerosas hipóteses colocadas para tentar resolver esta questão. O etnónimo olmeca foi cunhado pelos arqueólogos do século XX, e não devem confundir-se com os muito posteriores olmecas-xicalancas que ocuparam vários locais do México
Read more