Atomic Fedora failed to parse kernel config











up vote
0
down vote

favorite












i try to setup kubernetes cluster on atomic fedora. I tried atomic fedora 27, 28 and 29 but I am facing same error on every release.
Running kubeadm init ends with following error:



failed to parse kernel config: unable to load kernel module "configs": output - "modprobe: FATAL: Module configs not found in directory /lib/modules/4.19.5-200.fc28.x86_64n", err - exit status


I have tried to install the kernel-headers and kernel-devel, dracut regenerating, but nothing solved the issue. Do you have any idea how to solve it? And more important qustion, does someone have any idea what is causing the problem and what I am doing wrong?



Is this caused by the operating system or rather than misconfigured kubernetes?
I just tried to follow the atomic docs.










share|improve this question




























    up vote
    0
    down vote

    favorite












    i try to setup kubernetes cluster on atomic fedora. I tried atomic fedora 27, 28 and 29 but I am facing same error on every release.
    Running kubeadm init ends with following error:



    failed to parse kernel config: unable to load kernel module "configs": output - "modprobe: FATAL: Module configs not found in directory /lib/modules/4.19.5-200.fc28.x86_64n", err - exit status


    I have tried to install the kernel-headers and kernel-devel, dracut regenerating, but nothing solved the issue. Do you have any idea how to solve it? And more important qustion, does someone have any idea what is causing the problem and what I am doing wrong?



    Is this caused by the operating system or rather than misconfigured kubernetes?
    I just tried to follow the atomic docs.










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      i try to setup kubernetes cluster on atomic fedora. I tried atomic fedora 27, 28 and 29 but I am facing same error on every release.
      Running kubeadm init ends with following error:



      failed to parse kernel config: unable to load kernel module "configs": output - "modprobe: FATAL: Module configs not found in directory /lib/modules/4.19.5-200.fc28.x86_64n", err - exit status


      I have tried to install the kernel-headers and kernel-devel, dracut regenerating, but nothing solved the issue. Do you have any idea how to solve it? And more important qustion, does someone have any idea what is causing the problem and what I am doing wrong?



      Is this caused by the operating system or rather than misconfigured kubernetes?
      I just tried to follow the atomic docs.










      share|improve this question















      i try to setup kubernetes cluster on atomic fedora. I tried atomic fedora 27, 28 and 29 but I am facing same error on every release.
      Running kubeadm init ends with following error:



      failed to parse kernel config: unable to load kernel module "configs": output - "modprobe: FATAL: Module configs not found in directory /lib/modules/4.19.5-200.fc28.x86_64n", err - exit status


      I have tried to install the kernel-headers and kernel-devel, dracut regenerating, but nothing solved the issue. Do you have any idea how to solve it? And more important qustion, does someone have any idea what is causing the problem and what I am doing wrong?



      Is this caused by the operating system or rather than misconfigured kubernetes?
      I just tried to follow the atomic docs.







      fedora kernel kubernetes project-atomic






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 3 at 1:15









      Rui F Ribeiro

      38.5k1479128




      38.5k1479128










      asked Dec 2 at 23:13









      wintermute

      11




      11






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          kubeadm is looking in the wrong place for the kernel config (at least, based on where fedora atomic puts it). That'll eventually be fixed by this, but for now you need to append --ignore-preflight-errors=all to kubeadm init.






          share|improve this answer








          New contributor




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


















            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',
            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%2f485584%2fatomic-fedora-failed-to-parse-kernel-config%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








            up vote
            1
            down vote













            kubeadm is looking in the wrong place for the kernel config (at least, based on where fedora atomic puts it). That'll eventually be fixed by this, but for now you need to append --ignore-preflight-errors=all to kubeadm init.






            share|improve this answer








            New contributor




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






















              up vote
              1
              down vote













              kubeadm is looking in the wrong place for the kernel config (at least, based on where fedora atomic puts it). That'll eventually be fixed by this, but for now you need to append --ignore-preflight-errors=all to kubeadm init.






              share|improve this answer








              New contributor




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




















                up vote
                1
                down vote










                up vote
                1
                down vote









                kubeadm is looking in the wrong place for the kernel config (at least, based on where fedora atomic puts it). That'll eventually be fixed by this, but for now you need to append --ignore-preflight-errors=all to kubeadm init.






                share|improve this answer








                New contributor




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









                kubeadm is looking in the wrong place for the kernel config (at least, based on where fedora atomic puts it). That'll eventually be fixed by this, but for now you need to append --ignore-preflight-errors=all to kubeadm init.







                share|improve this answer








                New contributor




                jasonbrooks 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




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









                answered Dec 10 at 16:22









                jasonbrooks

                1113




                1113




                New contributor




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





                New contributor





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






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






























                    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.





                    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%2funix.stackexchange.com%2fquestions%2f485584%2fatomic-fedora-failed-to-parse-kernel-config%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

                    Morgemoulin

                    Scott Moir

                    Souastre