conjure-up cannot create user data directory





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















I have a new installation of Ubuntu 16.04 Server 64-bit. I am trying to setup a basic kubernetes environment using conjure-up.



First of all, I have installed conjure-up via snap as instructed on the Ubuntu documentation: https://docs.ubuntu.com/conjure-up/en/:



sudo snap install conjure-up --classic


It seems to go fine with the following message:



2017-08-07T07:53:04+03:00 INFO cannot auto connect core:core-support-plug to core:core-support: (slot auto-connection), existing connection state "core:core-support-plug core:core-support" in the way
conjure-up 2.2.2 from 'canonical' installed


Next, I run conjure-up kubernetes or even conjure-up without any params, it always fails and produces the following message:



cannot create user data directory: /home/local/DOMAIN/user/snap/conjure-up/549: Permission denied


I checked that folder and I could write into it without any problem, so I don't understand really what's going on.



Any ideas?










share|improve this question





























    1















    I have a new installation of Ubuntu 16.04 Server 64-bit. I am trying to setup a basic kubernetes environment using conjure-up.



    First of all, I have installed conjure-up via snap as instructed on the Ubuntu documentation: https://docs.ubuntu.com/conjure-up/en/:



    sudo snap install conjure-up --classic


    It seems to go fine with the following message:



    2017-08-07T07:53:04+03:00 INFO cannot auto connect core:core-support-plug to core:core-support: (slot auto-connection), existing connection state "core:core-support-plug core:core-support" in the way
    conjure-up 2.2.2 from 'canonical' installed


    Next, I run conjure-up kubernetes or even conjure-up without any params, it always fails and produces the following message:



    cannot create user data directory: /home/local/DOMAIN/user/snap/conjure-up/549: Permission denied


    I checked that folder and I could write into it without any problem, so I don't understand really what's going on.



    Any ideas?










    share|improve this question

























      1












      1








      1








      I have a new installation of Ubuntu 16.04 Server 64-bit. I am trying to setup a basic kubernetes environment using conjure-up.



      First of all, I have installed conjure-up via snap as instructed on the Ubuntu documentation: https://docs.ubuntu.com/conjure-up/en/:



      sudo snap install conjure-up --classic


      It seems to go fine with the following message:



      2017-08-07T07:53:04+03:00 INFO cannot auto connect core:core-support-plug to core:core-support: (slot auto-connection), existing connection state "core:core-support-plug core:core-support" in the way
      conjure-up 2.2.2 from 'canonical' installed


      Next, I run conjure-up kubernetes or even conjure-up without any params, it always fails and produces the following message:



      cannot create user data directory: /home/local/DOMAIN/user/snap/conjure-up/549: Permission denied


      I checked that folder and I could write into it without any problem, so I don't understand really what's going on.



      Any ideas?










      share|improve this question














      I have a new installation of Ubuntu 16.04 Server 64-bit. I am trying to setup a basic kubernetes environment using conjure-up.



      First of all, I have installed conjure-up via snap as instructed on the Ubuntu documentation: https://docs.ubuntu.com/conjure-up/en/:



      sudo snap install conjure-up --classic


      It seems to go fine with the following message:



      2017-08-07T07:53:04+03:00 INFO cannot auto connect core:core-support-plug to core:core-support: (slot auto-connection), existing connection state "core:core-support-plug core:core-support" in the way
      conjure-up 2.2.2 from 'canonical' installed


      Next, I run conjure-up kubernetes or even conjure-up without any params, it always fails and produces the following message:



      cannot create user data directory: /home/local/DOMAIN/user/snap/conjure-up/549: Permission denied


      I checked that folder and I could write into it without any problem, so I don't understand really what's going on.



      Any ideas?







      snap conjure-up kubernetes






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 7 '17 at 5:03









      SoCRaTSoCRaT

      815




      815






















          2 Answers
          2






          active

          oldest

          votes


















          3














          From the log message, it seems that your $HOME is mounted on a network filesystem, like NFS or CIFS.



          Currently there is a known limitation with snapd, that does not allow operation in such environment.



          See also Snaps with classic confinement and NFS /home.






          share|improve this answer


























          • I have this error and my home is on a different partition using a symbolic link. Is there a solution?

            – will
            Jan 29 at 12:33



















          1














          I was getting the same error while attempting to conjure-up kubernetes on Ubuntu 18.04 LTS. I was able to solve this by creating a file in /etc/apparmor.d/tunables/home.d with the contents @{HOMEDIRS}+=/home/DOMAIN/ (In your case it would be @{HOMEDIRS}+=/home/local/DOMAIN/).



          You'll have to sudo systemctl restart apparmor.service or reboot for the changes to take effect.






          share|improve this answer
























            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%2f943740%2fconjure-up-cannot-create-user-data-directory%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









            3














            From the log message, it seems that your $HOME is mounted on a network filesystem, like NFS or CIFS.



            Currently there is a known limitation with snapd, that does not allow operation in such environment.



            See also Snaps with classic confinement and NFS /home.






            share|improve this answer


























            • I have this error and my home is on a different partition using a symbolic link. Is there a solution?

              – will
              Jan 29 at 12:33
















            3














            From the log message, it seems that your $HOME is mounted on a network filesystem, like NFS or CIFS.



            Currently there is a known limitation with snapd, that does not allow operation in such environment.



            See also Snaps with classic confinement and NFS /home.






            share|improve this answer


























            • I have this error and my home is on a different partition using a symbolic link. Is there a solution?

              – will
              Jan 29 at 12:33














            3












            3








            3







            From the log message, it seems that your $HOME is mounted on a network filesystem, like NFS or CIFS.



            Currently there is a known limitation with snapd, that does not allow operation in such environment.



            See also Snaps with classic confinement and NFS /home.






            share|improve this answer















            From the log message, it seems that your $HOME is mounted on a network filesystem, like NFS or CIFS.



            Currently there is a known limitation with snapd, that does not allow operation in such environment.



            See also Snaps with classic confinement and NFS /home.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Aug 17 '17 at 9:43









            Eliah Kagan

            83.2k22229369




            83.2k22229369










            answered Aug 16 '17 at 0:11









            Michael I.Michael I.

            463




            463













            • I have this error and my home is on a different partition using a symbolic link. Is there a solution?

              – will
              Jan 29 at 12:33



















            • I have this error and my home is on a different partition using a symbolic link. Is there a solution?

              – will
              Jan 29 at 12:33

















            I have this error and my home is on a different partition using a symbolic link. Is there a solution?

            – will
            Jan 29 at 12:33





            I have this error and my home is on a different partition using a symbolic link. Is there a solution?

            – will
            Jan 29 at 12:33













            1














            I was getting the same error while attempting to conjure-up kubernetes on Ubuntu 18.04 LTS. I was able to solve this by creating a file in /etc/apparmor.d/tunables/home.d with the contents @{HOMEDIRS}+=/home/DOMAIN/ (In your case it would be @{HOMEDIRS}+=/home/local/DOMAIN/).



            You'll have to sudo systemctl restart apparmor.service or reboot for the changes to take effect.






            share|improve this answer




























              1














              I was getting the same error while attempting to conjure-up kubernetes on Ubuntu 18.04 LTS. I was able to solve this by creating a file in /etc/apparmor.d/tunables/home.d with the contents @{HOMEDIRS}+=/home/DOMAIN/ (In your case it would be @{HOMEDIRS}+=/home/local/DOMAIN/).



              You'll have to sudo systemctl restart apparmor.service or reboot for the changes to take effect.






              share|improve this answer


























                1












                1








                1







                I was getting the same error while attempting to conjure-up kubernetes on Ubuntu 18.04 LTS. I was able to solve this by creating a file in /etc/apparmor.d/tunables/home.d with the contents @{HOMEDIRS}+=/home/DOMAIN/ (In your case it would be @{HOMEDIRS}+=/home/local/DOMAIN/).



                You'll have to sudo systemctl restart apparmor.service or reboot for the changes to take effect.






                share|improve this answer













                I was getting the same error while attempting to conjure-up kubernetes on Ubuntu 18.04 LTS. I was able to solve this by creating a file in /etc/apparmor.d/tunables/home.d with the contents @{HOMEDIRS}+=/home/DOMAIN/ (In your case it would be @{HOMEDIRS}+=/home/local/DOMAIN/).



                You'll have to sudo systemctl restart apparmor.service or reboot for the changes to take effect.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 21 at 16:44









                Ryan StanleyRyan Stanley

                111




                111






























                    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%2f943740%2fconjure-up-cannot-create-user-data-directory%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

                    數位音樂下載

                    格利澤436b

                    When can things happen in Etherscan, such as the picture below?