Docker — WARNING: No swap limit support

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












17















I'm running Docker(1.9.1) on Ubuntu 16.04. When I run docker info the last line of the output says WARNING: No swap limit support.



INFO[0781] GET /v1.21/info 
Containers: 0
Images: 0
Server Version: 1.9.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 0
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.4.0-62-generic
Operating System: Ubuntu 16.04.1 LTS (containerized)
CPUs: 2
Total Memory: 3.664 GiB
Name: lenovo
ID: A3ZV:2EVK:U5QB:O7CG:PEDL:SANK:X74X:QNLC:VOTK:GFDR:S24T:C5KT
WARNING: No swap limit support


What does this warning mean? I definitely have a swap partition, as evidenced by free -mh though I don't understand why my swap has no entry under available



total used free shared buff/cache available
Mem: 3.7G 1.9G 182M 157M 1.6G 1.3G
Swap: 3.8G 2.9M 3.8G









share|improve this question


























    17















    I'm running Docker(1.9.1) on Ubuntu 16.04. When I run docker info the last line of the output says WARNING: No swap limit support.



    INFO[0781] GET /v1.21/info 
    Containers: 0
    Images: 0
    Server Version: 1.9.1
    Storage Driver: aufs
    Root Dir: /var/lib/docker/aufs
    Backing Filesystem: extfs
    Dirs: 0
    Dirperm1 Supported: true
    Execution Driver: native-0.2
    Logging Driver: json-file
    Kernel Version: 4.4.0-62-generic
    Operating System: Ubuntu 16.04.1 LTS (containerized)
    CPUs: 2
    Total Memory: 3.664 GiB
    Name: lenovo
    ID: A3ZV:2EVK:U5QB:O7CG:PEDL:SANK:X74X:QNLC:VOTK:GFDR:S24T:C5KT
    WARNING: No swap limit support


    What does this warning mean? I definitely have a swap partition, as evidenced by free -mh though I don't understand why my swap has no entry under available



    total used free shared buff/cache available
    Mem: 3.7G 1.9G 182M 157M 1.6G 1.3G
    Swap: 3.8G 2.9M 3.8G









    share|improve this question
























      17












      17








      17


      1






      I'm running Docker(1.9.1) on Ubuntu 16.04. When I run docker info the last line of the output says WARNING: No swap limit support.



      INFO[0781] GET /v1.21/info 
      Containers: 0
      Images: 0
      Server Version: 1.9.1
      Storage Driver: aufs
      Root Dir: /var/lib/docker/aufs
      Backing Filesystem: extfs
      Dirs: 0
      Dirperm1 Supported: true
      Execution Driver: native-0.2
      Logging Driver: json-file
      Kernel Version: 4.4.0-62-generic
      Operating System: Ubuntu 16.04.1 LTS (containerized)
      CPUs: 2
      Total Memory: 3.664 GiB
      Name: lenovo
      ID: A3ZV:2EVK:U5QB:O7CG:PEDL:SANK:X74X:QNLC:VOTK:GFDR:S24T:C5KT
      WARNING: No swap limit support


      What does this warning mean? I definitely have a swap partition, as evidenced by free -mh though I don't understand why my swap has no entry under available



      total used free shared buff/cache available
      Mem: 3.7G 1.9G 182M 157M 1.6G 1.3G
      Swap: 3.8G 2.9M 3.8G









      share|improve this question














      I'm running Docker(1.9.1) on Ubuntu 16.04. When I run docker info the last line of the output says WARNING: No swap limit support.



      INFO[0781] GET /v1.21/info 
      Containers: 0
      Images: 0
      Server Version: 1.9.1
      Storage Driver: aufs
      Root Dir: /var/lib/docker/aufs
      Backing Filesystem: extfs
      Dirs: 0
      Dirperm1 Supported: true
      Execution Driver: native-0.2
      Logging Driver: json-file
      Kernel Version: 4.4.0-62-generic
      Operating System: Ubuntu 16.04.1 LTS (containerized)
      CPUs: 2
      Total Memory: 3.664 GiB
      Name: lenovo
      ID: A3ZV:2EVK:U5QB:O7CG:PEDL:SANK:X74X:QNLC:VOTK:GFDR:S24T:C5KT
      WARNING: No swap limit support


      What does this warning mean? I definitely have a swap partition, as evidenced by free -mh though I don't understand why my swap has no entry under available



      total used free shared buff/cache available
      Mem: 3.7G 1.9G 182M 157M 1.6G 1.3G
      Swap: 3.8G 2.9M 3.8G






      swap docker






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 5 '17 at 21:16









      Stephen CStephen C

      346316




      346316




















          2 Answers
          2






          active

          oldest

          votes


















          16














          Swap limit support allows you to limit the swap the container uses, see https://docs.docker.com/engine/admin/resource_constraints



          According to https://docs.docker.com/engine/installation/linux/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities :




          You can enable these capabilities on Ubuntu or Debian by following
          these instructions. Memory and swap accounting incur an overhead of
          about 1% of the total available memory and a 10% overall performance
          degradation, even if Docker is not running.



          1) Log into the Ubuntu or Debian host as a user with sudo privileges.



          2) Edit the /etc/default/grub file. Add or edit the GRUB_CMDLINE_LINUX line to add the following two key-value pairs:



          GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1"


          3) Update GRUB.



          $ sudo update-grub






          share|improve this answer






























            0














            Well for me it's been like this:




            1. edit the file /etc/default/grub.d/50-cloudimg-settings.cfg and edit the line to GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0 cgroup_enable=memory swapaccount=1"



              sudo nano /etc/default/grub.d/50-cloudimg-settings.cfg




            2. update grup



              sudo update-grub




            3. reboot



              sudo reboot







            share|improve this answer






















              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "106"
              ;
              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: false,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              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%2funix.stackexchange.com%2fquestions%2f342735%2fdocker-warning-no-swap-limit-support%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              16














              Swap limit support allows you to limit the swap the container uses, see https://docs.docker.com/engine/admin/resource_constraints



              According to https://docs.docker.com/engine/installation/linux/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities :




              You can enable these capabilities on Ubuntu or Debian by following
              these instructions. Memory and swap accounting incur an overhead of
              about 1% of the total available memory and a 10% overall performance
              degradation, even if Docker is not running.



              1) Log into the Ubuntu or Debian host as a user with sudo privileges.



              2) Edit the /etc/default/grub file. Add or edit the GRUB_CMDLINE_LINUX line to add the following two key-value pairs:



              GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1"


              3) Update GRUB.



              $ sudo update-grub






              share|improve this answer



























                16














                Swap limit support allows you to limit the swap the container uses, see https://docs.docker.com/engine/admin/resource_constraints



                According to https://docs.docker.com/engine/installation/linux/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities :




                You can enable these capabilities on Ubuntu or Debian by following
                these instructions. Memory and swap accounting incur an overhead of
                about 1% of the total available memory and a 10% overall performance
                degradation, even if Docker is not running.



                1) Log into the Ubuntu or Debian host as a user with sudo privileges.



                2) Edit the /etc/default/grub file. Add or edit the GRUB_CMDLINE_LINUX line to add the following two key-value pairs:



                GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1"


                3) Update GRUB.



                $ sudo update-grub






                share|improve this answer

























                  16












                  16








                  16







                  Swap limit support allows you to limit the swap the container uses, see https://docs.docker.com/engine/admin/resource_constraints



                  According to https://docs.docker.com/engine/installation/linux/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities :




                  You can enable these capabilities on Ubuntu or Debian by following
                  these instructions. Memory and swap accounting incur an overhead of
                  about 1% of the total available memory and a 10% overall performance
                  degradation, even if Docker is not running.



                  1) Log into the Ubuntu or Debian host as a user with sudo privileges.



                  2) Edit the /etc/default/grub file. Add or edit the GRUB_CMDLINE_LINUX line to add the following two key-value pairs:



                  GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1"


                  3) Update GRUB.



                  $ sudo update-grub






                  share|improve this answer













                  Swap limit support allows you to limit the swap the container uses, see https://docs.docker.com/engine/admin/resource_constraints



                  According to https://docs.docker.com/engine/installation/linux/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities :




                  You can enable these capabilities on Ubuntu or Debian by following
                  these instructions. Memory and swap accounting incur an overhead of
                  about 1% of the total available memory and a 10% overall performance
                  degradation, even if Docker is not running.



                  1) Log into the Ubuntu or Debian host as a user with sudo privileges.



                  2) Edit the /etc/default/grub file. Add or edit the GRUB_CMDLINE_LINUX line to add the following two key-value pairs:



                  GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1"


                  3) Update GRUB.



                  $ sudo update-grub







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 5 '17 at 15:18









                  SamizdisSamizdis

                  27827




                  27827























                      0














                      Well for me it's been like this:




                      1. edit the file /etc/default/grub.d/50-cloudimg-settings.cfg and edit the line to GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0 cgroup_enable=memory swapaccount=1"



                        sudo nano /etc/default/grub.d/50-cloudimg-settings.cfg




                      2. update grup



                        sudo update-grub




                      3. reboot



                        sudo reboot







                      share|improve this answer



























                        0














                        Well for me it's been like this:




                        1. edit the file /etc/default/grub.d/50-cloudimg-settings.cfg and edit the line to GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0 cgroup_enable=memory swapaccount=1"



                          sudo nano /etc/default/grub.d/50-cloudimg-settings.cfg




                        2. update grup



                          sudo update-grub




                        3. reboot



                          sudo reboot







                        share|improve this answer

























                          0












                          0








                          0







                          Well for me it's been like this:




                          1. edit the file /etc/default/grub.d/50-cloudimg-settings.cfg and edit the line to GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0 cgroup_enable=memory swapaccount=1"



                            sudo nano /etc/default/grub.d/50-cloudimg-settings.cfg




                          2. update grup



                            sudo update-grub




                          3. reboot



                            sudo reboot







                          share|improve this answer













                          Well for me it's been like this:




                          1. edit the file /etc/default/grub.d/50-cloudimg-settings.cfg and edit the line to GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0 cgroup_enable=memory swapaccount=1"



                            sudo nano /etc/default/grub.d/50-cloudimg-settings.cfg




                          2. update grup



                            sudo update-grub




                          3. reboot



                            sudo reboot








                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jan 17 at 13:54









                          KaiKai

                          1011




                          1011



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Unix & Linux Stack Exchange!


                              • 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%2funix.stackexchange.com%2fquestions%2f342735%2fdocker-warning-no-swap-limit-support%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

                              How to check contact read email or not when send email to Individual?

                              Displaying single band from multi-band raster using QGIS

                              How many registers does an x86_64 CPU actually have?