Which kubernetes version is supported in docker version 18.09











up vote
3
down vote

favorite
2












I am using Raspberry pi for kubernetes cluster setup. I was using below docker version:



Client:
Version: 18.06.1-ce
API version: 1.38
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:30:52 2018
OS/Arch: linux/arm
Experimental: false

Server:
Engine:
Version: 18.06.1-ce
API version: 1.38 (minimum version 1.12)
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:26:37 2018
OS/Arch: linux/arm
Experimental: false


Looks like now the docker version latest is 18.09.0 and the latest kubernetes version is not supporting this docker version. I have even tried installing some older version of kube like 1.9.7 or 1.9.6 but while initiating the kubeadm init, I am getting the below error:



[ERROR SystemVerification]: unsupported docker version: 18.09.0
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`


Which version should I specify for kubernetes and docker to run properly. Also how can we specify version while insatlling docker. I normally use below command to install docker:



curl -sSL get.docker.com | sh 









share|improve this question


























    up vote
    3
    down vote

    favorite
    2












    I am using Raspberry pi for kubernetes cluster setup. I was using below docker version:



    Client:
    Version: 18.06.1-ce
    API version: 1.38
    Go version: go1.10.3
    Git commit: e68fc7a
    Built: Tue Aug 21 17:30:52 2018
    OS/Arch: linux/arm
    Experimental: false

    Server:
    Engine:
    Version: 18.06.1-ce
    API version: 1.38 (minimum version 1.12)
    Go version: go1.10.3
    Git commit: e68fc7a
    Built: Tue Aug 21 17:26:37 2018
    OS/Arch: linux/arm
    Experimental: false


    Looks like now the docker version latest is 18.09.0 and the latest kubernetes version is not supporting this docker version. I have even tried installing some older version of kube like 1.9.7 or 1.9.6 but while initiating the kubeadm init, I am getting the below error:



    [ERROR SystemVerification]: unsupported docker version: 18.09.0
    [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`


    Which version should I specify for kubernetes and docker to run properly. Also how can we specify version while insatlling docker. I normally use below command to install docker:



    curl -sSL get.docker.com | sh 









    share|improve this question
























      up vote
      3
      down vote

      favorite
      2









      up vote
      3
      down vote

      favorite
      2






      2





      I am using Raspberry pi for kubernetes cluster setup. I was using below docker version:



      Client:
      Version: 18.06.1-ce
      API version: 1.38
      Go version: go1.10.3
      Git commit: e68fc7a
      Built: Tue Aug 21 17:30:52 2018
      OS/Arch: linux/arm
      Experimental: false

      Server:
      Engine:
      Version: 18.06.1-ce
      API version: 1.38 (minimum version 1.12)
      Go version: go1.10.3
      Git commit: e68fc7a
      Built: Tue Aug 21 17:26:37 2018
      OS/Arch: linux/arm
      Experimental: false


      Looks like now the docker version latest is 18.09.0 and the latest kubernetes version is not supporting this docker version. I have even tried installing some older version of kube like 1.9.7 or 1.9.6 but while initiating the kubeadm init, I am getting the below error:



      [ERROR SystemVerification]: unsupported docker version: 18.09.0
      [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`


      Which version should I specify for kubernetes and docker to run properly. Also how can we specify version while insatlling docker. I normally use below command to install docker:



      curl -sSL get.docker.com | sh 









      share|improve this question













      I am using Raspberry pi for kubernetes cluster setup. I was using below docker version:



      Client:
      Version: 18.06.1-ce
      API version: 1.38
      Go version: go1.10.3
      Git commit: e68fc7a
      Built: Tue Aug 21 17:30:52 2018
      OS/Arch: linux/arm
      Experimental: false

      Server:
      Engine:
      Version: 18.06.1-ce
      API version: 1.38 (minimum version 1.12)
      Go version: go1.10.3
      Git commit: e68fc7a
      Built: Tue Aug 21 17:26:37 2018
      OS/Arch: linux/arm
      Experimental: false


      Looks like now the docker version latest is 18.09.0 and the latest kubernetes version is not supporting this docker version. I have even tried installing some older version of kube like 1.9.7 or 1.9.6 but while initiating the kubeadm init, I am getting the below error:



      [ERROR SystemVerification]: unsupported docker version: 18.09.0
      [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`


      Which version should I specify for kubernetes and docker to run properly. Also how can we specify version while insatlling docker. I normally use below command to install docker:



      curl -sSL get.docker.com | sh 






      docker kubernetes version






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 12 at 6:13









      S Andrew

      671735




      671735
























          4 Answers
          4






          active

          oldest

          votes

















          up vote
          8
          down vote



          accepted










          In Kubernetes there is nothing like supported. Instead of it they use validated - it means that all features were tested and validated with some Docker version.



          And validated Docker versions are still the same from Kubernetes version 1.8 until 1.11: Docker 1.11.2 to 1.13.1 and 17.03.x. See here:
          https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.8.md#external-dependencies
          and here https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md#external-dependencies



          Starting from Kubernetes version 1.12 Docker 17.06, 17.09 and 18.06 started to be also validated. See here:
          https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.12.md#external-dependencies



          As I know final version of Docker 18.09 was released 4 days ago so here we cannot expect this version to be validated in Kubernetes now.





          You can specify exact Docker version for the get.docker.com script by VERSION variable:



          export VERSION=18.03 && curl -sSL get.docker.com | sh





          share|improve this answer























          • Where should I put this variable definition so that get.docker.script could see it?
            – pensnarik
            Dec 3 at 7:04










          • You can use that "one line" command or explicitly run export VERSION=18.06 and then in the second step curl -sSL get.docker.com | sh. It is an environment variable.
            – cgrim
            Dec 3 at 7:42


















          up vote
          1
          down vote













          As mentioned above, the message is more of a warning that not all features were tested against that specific Docker release. On your own risk, you can try to temporarily ignore those errors by using the --ignore-preflight-errors flag. Eg :
          kubedam init --ignore-preflight-errors all






          share|improve this answer




























            up vote
            0
            down vote













            Here's how I "fixed" mine:



            $ sudo kubeadm init --ignore-preflight-errors=SystemVerification
            ...
            [WARNING SystemVerification]: unsupported docker version: 18.09.0


            Here's what I saw when "preflight errors" were not ignored:



            $ sudo kubeadm init
            ...
            [preflight] Some fatal errors occurred:
            [ERROR SystemVerification]: unsupported docker version: 18.09.0
            [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`


            Here's the version of kubeadm I used:



            $ kubeadm version --output json
            {
            "clientVersion": {
            "major": "1",
            "minor": "12",
            "gitVersion": "v1.12.2",
            "gitCommit": "17c77c7898218073f14c8d573582e8d2313dc740",
            "gitTreeState": "clean",
            "buildDate": "2018-10-24T06:51:33Z",
            "goVersion": "go1.10.4",
            "compiler": "gc",
            "platform": "linux/amd64"
            }
            }





            share|improve this answer






























              up vote
              0
              down vote













              I solved this problem as:





              kubeadm init --ignore-preflight-errors=SystemVerification








              share|improve this answer





















                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',
                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%2f53256739%2fwhich-kubernetes-version-is-supported-in-docker-version-18-09%23new-answer', 'question_page');
                }
                );

                Post as a guest















                Required, but never shown

























                4 Answers
                4






                active

                oldest

                votes








                4 Answers
                4






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes








                up vote
                8
                down vote



                accepted










                In Kubernetes there is nothing like supported. Instead of it they use validated - it means that all features were tested and validated with some Docker version.



                And validated Docker versions are still the same from Kubernetes version 1.8 until 1.11: Docker 1.11.2 to 1.13.1 and 17.03.x. See here:
                https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.8.md#external-dependencies
                and here https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md#external-dependencies



                Starting from Kubernetes version 1.12 Docker 17.06, 17.09 and 18.06 started to be also validated. See here:
                https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.12.md#external-dependencies



                As I know final version of Docker 18.09 was released 4 days ago so here we cannot expect this version to be validated in Kubernetes now.





                You can specify exact Docker version for the get.docker.com script by VERSION variable:



                export VERSION=18.03 && curl -sSL get.docker.com | sh





                share|improve this answer























                • Where should I put this variable definition so that get.docker.script could see it?
                  – pensnarik
                  Dec 3 at 7:04










                • You can use that "one line" command or explicitly run export VERSION=18.06 and then in the second step curl -sSL get.docker.com | sh. It is an environment variable.
                  – cgrim
                  Dec 3 at 7:42















                up vote
                8
                down vote



                accepted










                In Kubernetes there is nothing like supported. Instead of it they use validated - it means that all features were tested and validated with some Docker version.



                And validated Docker versions are still the same from Kubernetes version 1.8 until 1.11: Docker 1.11.2 to 1.13.1 and 17.03.x. See here:
                https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.8.md#external-dependencies
                and here https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md#external-dependencies



                Starting from Kubernetes version 1.12 Docker 17.06, 17.09 and 18.06 started to be also validated. See here:
                https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.12.md#external-dependencies



                As I know final version of Docker 18.09 was released 4 days ago so here we cannot expect this version to be validated in Kubernetes now.





                You can specify exact Docker version for the get.docker.com script by VERSION variable:



                export VERSION=18.03 && curl -sSL get.docker.com | sh





                share|improve this answer























                • Where should I put this variable definition so that get.docker.script could see it?
                  – pensnarik
                  Dec 3 at 7:04










                • You can use that "one line" command or explicitly run export VERSION=18.06 and then in the second step curl -sSL get.docker.com | sh. It is an environment variable.
                  – cgrim
                  Dec 3 at 7:42













                up vote
                8
                down vote



                accepted







                up vote
                8
                down vote



                accepted






                In Kubernetes there is nothing like supported. Instead of it they use validated - it means that all features were tested and validated with some Docker version.



                And validated Docker versions are still the same from Kubernetes version 1.8 until 1.11: Docker 1.11.2 to 1.13.1 and 17.03.x. See here:
                https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.8.md#external-dependencies
                and here https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md#external-dependencies



                Starting from Kubernetes version 1.12 Docker 17.06, 17.09 and 18.06 started to be also validated. See here:
                https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.12.md#external-dependencies



                As I know final version of Docker 18.09 was released 4 days ago so here we cannot expect this version to be validated in Kubernetes now.





                You can specify exact Docker version for the get.docker.com script by VERSION variable:



                export VERSION=18.03 && curl -sSL get.docker.com | sh





                share|improve this answer














                In Kubernetes there is nothing like supported. Instead of it they use validated - it means that all features were tested and validated with some Docker version.



                And validated Docker versions are still the same from Kubernetes version 1.8 until 1.11: Docker 1.11.2 to 1.13.1 and 17.03.x. See here:
                https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.8.md#external-dependencies
                and here https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md#external-dependencies



                Starting from Kubernetes version 1.12 Docker 17.06, 17.09 and 18.06 started to be also validated. See here:
                https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.12.md#external-dependencies



                As I know final version of Docker 18.09 was released 4 days ago so here we cannot expect this version to be validated in Kubernetes now.





                You can specify exact Docker version for the get.docker.com script by VERSION variable:



                export VERSION=18.03 && curl -sSL get.docker.com | sh






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 12 at 20:34

























                answered Nov 12 at 7:44









                cgrim

                1,1281418




                1,1281418












                • Where should I put this variable definition so that get.docker.script could see it?
                  – pensnarik
                  Dec 3 at 7:04










                • You can use that "one line" command or explicitly run export VERSION=18.06 and then in the second step curl -sSL get.docker.com | sh. It is an environment variable.
                  – cgrim
                  Dec 3 at 7:42


















                • Where should I put this variable definition so that get.docker.script could see it?
                  – pensnarik
                  Dec 3 at 7:04










                • You can use that "one line" command or explicitly run export VERSION=18.06 and then in the second step curl -sSL get.docker.com | sh. It is an environment variable.
                  – cgrim
                  Dec 3 at 7:42
















                Where should I put this variable definition so that get.docker.script could see it?
                – pensnarik
                Dec 3 at 7:04




                Where should I put this variable definition so that get.docker.script could see it?
                – pensnarik
                Dec 3 at 7:04












                You can use that "one line" command or explicitly run export VERSION=18.06 and then in the second step curl -sSL get.docker.com | sh. It is an environment variable.
                – cgrim
                Dec 3 at 7:42




                You can use that "one line" command or explicitly run export VERSION=18.06 and then in the second step curl -sSL get.docker.com | sh. It is an environment variable.
                – cgrim
                Dec 3 at 7:42












                up vote
                1
                down vote













                As mentioned above, the message is more of a warning that not all features were tested against that specific Docker release. On your own risk, you can try to temporarily ignore those errors by using the --ignore-preflight-errors flag. Eg :
                kubedam init --ignore-preflight-errors all






                share|improve this answer

























                  up vote
                  1
                  down vote













                  As mentioned above, the message is more of a warning that not all features were tested against that specific Docker release. On your own risk, you can try to temporarily ignore those errors by using the --ignore-preflight-errors flag. Eg :
                  kubedam init --ignore-preflight-errors all






                  share|improve this answer























                    up vote
                    1
                    down vote










                    up vote
                    1
                    down vote









                    As mentioned above, the message is more of a warning that not all features were tested against that specific Docker release. On your own risk, you can try to temporarily ignore those errors by using the --ignore-preflight-errors flag. Eg :
                    kubedam init --ignore-preflight-errors all






                    share|improve this answer












                    As mentioned above, the message is more of a warning that not all features were tested against that specific Docker release. On your own risk, you can try to temporarily ignore those errors by using the --ignore-preflight-errors flag. Eg :
                    kubedam init --ignore-preflight-errors all







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Nov 22 at 23:21









                    Daniel

                    111




                    111






















                        up vote
                        0
                        down vote













                        Here's how I "fixed" mine:



                        $ sudo kubeadm init --ignore-preflight-errors=SystemVerification
                        ...
                        [WARNING SystemVerification]: unsupported docker version: 18.09.0


                        Here's what I saw when "preflight errors" were not ignored:



                        $ sudo kubeadm init
                        ...
                        [preflight] Some fatal errors occurred:
                        [ERROR SystemVerification]: unsupported docker version: 18.09.0
                        [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`


                        Here's the version of kubeadm I used:



                        $ kubeadm version --output json
                        {
                        "clientVersion": {
                        "major": "1",
                        "minor": "12",
                        "gitVersion": "v1.12.2",
                        "gitCommit": "17c77c7898218073f14c8d573582e8d2313dc740",
                        "gitTreeState": "clean",
                        "buildDate": "2018-10-24T06:51:33Z",
                        "goVersion": "go1.10.4",
                        "compiler": "gc",
                        "platform": "linux/amd64"
                        }
                        }





                        share|improve this answer



























                          up vote
                          0
                          down vote













                          Here's how I "fixed" mine:



                          $ sudo kubeadm init --ignore-preflight-errors=SystemVerification
                          ...
                          [WARNING SystemVerification]: unsupported docker version: 18.09.0


                          Here's what I saw when "preflight errors" were not ignored:



                          $ sudo kubeadm init
                          ...
                          [preflight] Some fatal errors occurred:
                          [ERROR SystemVerification]: unsupported docker version: 18.09.0
                          [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`


                          Here's the version of kubeadm I used:



                          $ kubeadm version --output json
                          {
                          "clientVersion": {
                          "major": "1",
                          "minor": "12",
                          "gitVersion": "v1.12.2",
                          "gitCommit": "17c77c7898218073f14c8d573582e8d2313dc740",
                          "gitTreeState": "clean",
                          "buildDate": "2018-10-24T06:51:33Z",
                          "goVersion": "go1.10.4",
                          "compiler": "gc",
                          "platform": "linux/amd64"
                          }
                          }





                          share|improve this answer

























                            up vote
                            0
                            down vote










                            up vote
                            0
                            down vote









                            Here's how I "fixed" mine:



                            $ sudo kubeadm init --ignore-preflight-errors=SystemVerification
                            ...
                            [WARNING SystemVerification]: unsupported docker version: 18.09.0


                            Here's what I saw when "preflight errors" were not ignored:



                            $ sudo kubeadm init
                            ...
                            [preflight] Some fatal errors occurred:
                            [ERROR SystemVerification]: unsupported docker version: 18.09.0
                            [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`


                            Here's the version of kubeadm I used:



                            $ kubeadm version --output json
                            {
                            "clientVersion": {
                            "major": "1",
                            "minor": "12",
                            "gitVersion": "v1.12.2",
                            "gitCommit": "17c77c7898218073f14c8d573582e8d2313dc740",
                            "gitTreeState": "clean",
                            "buildDate": "2018-10-24T06:51:33Z",
                            "goVersion": "go1.10.4",
                            "compiler": "gc",
                            "platform": "linux/amd64"
                            }
                            }





                            share|improve this answer














                            Here's how I "fixed" mine:



                            $ sudo kubeadm init --ignore-preflight-errors=SystemVerification
                            ...
                            [WARNING SystemVerification]: unsupported docker version: 18.09.0


                            Here's what I saw when "preflight errors" were not ignored:



                            $ sudo kubeadm init
                            ...
                            [preflight] Some fatal errors occurred:
                            [ERROR SystemVerification]: unsupported docker version: 18.09.0
                            [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`


                            Here's the version of kubeadm I used:



                            $ kubeadm version --output json
                            {
                            "clientVersion": {
                            "major": "1",
                            "minor": "12",
                            "gitVersion": "v1.12.2",
                            "gitCommit": "17c77c7898218073f14c8d573582e8d2313dc740",
                            "gitTreeState": "clean",
                            "buildDate": "2018-10-24T06:51:33Z",
                            "goVersion": "go1.10.4",
                            "compiler": "gc",
                            "platform": "linux/amd64"
                            }
                            }






                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Nov 23 at 20:43

























                            answered Nov 23 at 20:33









                            rubicks

                            2,2771722




                            2,2771722






















                                up vote
                                0
                                down vote













                                I solved this problem as:





                                kubeadm init --ignore-preflight-errors=SystemVerification








                                share|improve this answer

























                                  up vote
                                  0
                                  down vote













                                  I solved this problem as:





                                  kubeadm init --ignore-preflight-errors=SystemVerification








                                  share|improve this answer























                                    up vote
                                    0
                                    down vote










                                    up vote
                                    0
                                    down vote









                                    I solved this problem as:





                                    kubeadm init --ignore-preflight-errors=SystemVerification








                                    share|improve this answer












                                    I solved this problem as:





                                    kubeadm init --ignore-preflight-errors=SystemVerification









                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Nov 27 at 23:55









                                    alexvirtualbr

                                    1




                                    1






























                                        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.





                                        Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                                        Please pay close attention to the following guidance:


                                        • 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%2f53256739%2fwhich-kubernetes-version-is-supported-in-docker-version-18-09%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

                                        Guess what letter conforming each word

                                        Port of Spain

                                        Run scheduled task as local user group (not BUILTIN)