Docker child processes do not inherit niceness of daemon












1















I often run a lot of docker containers, which sometimes cause my system to freeze momentarily. To prevent this, I made a service that automatically sets the niceness of docker-containerd a bit higher. I thought that this would cause all new child processes to inherit this niceness, but when I start a new container all processes have a niceness of 0



Here is a screenshot of htop



I'm not sure if this is caused by howDocker works internally or something else (cgroups perhaps?).



Does anybody have an idea how I could automatically give all containers-processes a higher niceness? I don´t want to use the docker-specific features like --cpu-period, since that means I'll have to specify these arguments each time that I create a new container.










share|improve this question



























    1















    I often run a lot of docker containers, which sometimes cause my system to freeze momentarily. To prevent this, I made a service that automatically sets the niceness of docker-containerd a bit higher. I thought that this would cause all new child processes to inherit this niceness, but when I start a new container all processes have a niceness of 0



    Here is a screenshot of htop



    I'm not sure if this is caused by howDocker works internally or something else (cgroups perhaps?).



    Does anybody have an idea how I could automatically give all containers-processes a higher niceness? I don´t want to use the docker-specific features like --cpu-period, since that means I'll have to specify these arguments each time that I create a new container.










    share|improve this question

























      1












      1








      1








      I often run a lot of docker containers, which sometimes cause my system to freeze momentarily. To prevent this, I made a service that automatically sets the niceness of docker-containerd a bit higher. I thought that this would cause all new child processes to inherit this niceness, but when I start a new container all processes have a niceness of 0



      Here is a screenshot of htop



      I'm not sure if this is caused by howDocker works internally or something else (cgroups perhaps?).



      Does anybody have an idea how I could automatically give all containers-processes a higher niceness? I don´t want to use the docker-specific features like --cpu-period, since that means I'll have to specify these arguments each time that I create a new container.










      share|improve this question














      I often run a lot of docker containers, which sometimes cause my system to freeze momentarily. To prevent this, I made a service that automatically sets the niceness of docker-containerd a bit higher. I thought that this would cause all new child processes to inherit this niceness, but when I start a new container all processes have a niceness of 0



      Here is a screenshot of htop



      I'm not sure if this is caused by howDocker works internally or something else (cgroups perhaps?).



      Does anybody have an idea how I could automatically give all containers-processes a higher niceness? I don´t want to use the docker-specific features like --cpu-period, since that means I'll have to specify these arguments each time that I create a new container.







      docker nice cgroup






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 22 '17 at 10:59









      Vinno97Vinno97

      164




      164






















          1 Answer
          1






          active

          oldest

          votes


















          0














          its the other way round for me. All my containers inherit the nice level from dockerd. But I want only dockerd to run in higher priority.






          share|improve this answer








          New contributor




          Saravana Kumar Periyasamy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.
















          • 2





            This is how I would expect it to work, since child processes inherit the niceness of their parent when they get spawned. I made this post over a year ago and I don't remember the specifics. You could try to change the niceness of the daemon after the containers are started. This post does a quite decent job of explaining niceness: unix.stackexchange.com/a/37901/273800

            – Vinno97
            9 hours ago













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          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%2faskubuntu.com%2fquestions%2f979098%2fdocker-child-processes-do-not-inherit-niceness-of-daemon%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          its the other way round for me. All my containers inherit the nice level from dockerd. But I want only dockerd to run in higher priority.






          share|improve this answer








          New contributor




          Saravana Kumar Periyasamy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.
















          • 2





            This is how I would expect it to work, since child processes inherit the niceness of their parent when they get spawned. I made this post over a year ago and I don't remember the specifics. You could try to change the niceness of the daemon after the containers are started. This post does a quite decent job of explaining niceness: unix.stackexchange.com/a/37901/273800

            – Vinno97
            9 hours ago


















          0














          its the other way round for me. All my containers inherit the nice level from dockerd. But I want only dockerd to run in higher priority.






          share|improve this answer








          New contributor




          Saravana Kumar Periyasamy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.
















          • 2





            This is how I would expect it to work, since child processes inherit the niceness of their parent when they get spawned. I made this post over a year ago and I don't remember the specifics. You could try to change the niceness of the daemon after the containers are started. This post does a quite decent job of explaining niceness: unix.stackexchange.com/a/37901/273800

            – Vinno97
            9 hours ago
















          0












          0








          0







          its the other way round for me. All my containers inherit the nice level from dockerd. But I want only dockerd to run in higher priority.






          share|improve this answer








          New contributor




          Saravana Kumar Periyasamy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.










          its the other way round for me. All my containers inherit the nice level from dockerd. But I want only dockerd to run in higher priority.







          share|improve this answer








          New contributor




          Saravana Kumar Periyasamy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          share|improve this answer



          share|improve this answer






          New contributor




          Saravana Kumar Periyasamy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          answered 10 hours ago









          Saravana Kumar PeriyasamySaravana Kumar Periyasamy

          1




          1




          New contributor




          Saravana Kumar Periyasamy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





          New contributor





          Saravana Kumar Periyasamy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.






          Saravana Kumar Periyasamy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.








          • 2





            This is how I would expect it to work, since child processes inherit the niceness of their parent when they get spawned. I made this post over a year ago and I don't remember the specifics. You could try to change the niceness of the daemon after the containers are started. This post does a quite decent job of explaining niceness: unix.stackexchange.com/a/37901/273800

            – Vinno97
            9 hours ago
















          • 2





            This is how I would expect it to work, since child processes inherit the niceness of their parent when they get spawned. I made this post over a year ago and I don't remember the specifics. You could try to change the niceness of the daemon after the containers are started. This post does a quite decent job of explaining niceness: unix.stackexchange.com/a/37901/273800

            – Vinno97
            9 hours ago










          2




          2





          This is how I would expect it to work, since child processes inherit the niceness of their parent when they get spawned. I made this post over a year ago and I don't remember the specifics. You could try to change the niceness of the daemon after the containers are started. This post does a quite decent job of explaining niceness: unix.stackexchange.com/a/37901/273800

          – Vinno97
          9 hours ago







          This is how I would expect it to work, since child processes inherit the niceness of their parent when they get spawned. I made this post over a year ago and I don't remember the specifics. You could try to change the niceness of the daemon after the containers are started. This post does a quite decent job of explaining niceness: unix.stackexchange.com/a/37901/273800

          – Vinno97
          9 hours ago




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • 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%2faskubuntu.com%2fquestions%2f979098%2fdocker-child-processes-do-not-inherit-niceness-of-daemon%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

          GameSpot

          connect to host localhost port 22: Connection refused

          Getting a Wifi WPA2 wifi connection