Setting up Heroku CLI in WSL












0















Trying to setup Heroku CLI to work with WSL.



Starting by following the directions here for Ubuntu 16+:



https://devcenter.heroku.com/articles/heroku-cli



sudo snap install --classic heroku



Produces the following error:




error: cannot communicate with server: Post http://localhost/v2/snaps/heroku: dial unix /run/snapd.socket: connect: no such file or directory




Googled the error and came across this thread:



https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1631514



I tried systemctl status snapd.service, which just says the following:




System has not been booted with systemd as init system (PID 1). Can't operate.




Restart WSL and the computer and same issue.



Thought maybe snapd wasn't installed because typing snap or snapd says Command '____' not found, did you mean:.... But trying to do sudo apt-get install snapd says that it is already the latest version.










share|improve this question



























    0















    Trying to setup Heroku CLI to work with WSL.



    Starting by following the directions here for Ubuntu 16+:



    https://devcenter.heroku.com/articles/heroku-cli



    sudo snap install --classic heroku



    Produces the following error:




    error: cannot communicate with server: Post http://localhost/v2/snaps/heroku: dial unix /run/snapd.socket: connect: no such file or directory




    Googled the error and came across this thread:



    https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1631514



    I tried systemctl status snapd.service, which just says the following:




    System has not been booted with systemd as init system (PID 1). Can't operate.




    Restart WSL and the computer and same issue.



    Thought maybe snapd wasn't installed because typing snap or snapd says Command '____' not found, did you mean:.... But trying to do sudo apt-get install snapd says that it is already the latest version.










    share|improve this question

























      0












      0








      0








      Trying to setup Heroku CLI to work with WSL.



      Starting by following the directions here for Ubuntu 16+:



      https://devcenter.heroku.com/articles/heroku-cli



      sudo snap install --classic heroku



      Produces the following error:




      error: cannot communicate with server: Post http://localhost/v2/snaps/heroku: dial unix /run/snapd.socket: connect: no such file or directory




      Googled the error and came across this thread:



      https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1631514



      I tried systemctl status snapd.service, which just says the following:




      System has not been booted with systemd as init system (PID 1). Can't operate.




      Restart WSL and the computer and same issue.



      Thought maybe snapd wasn't installed because typing snap or snapd says Command '____' not found, did you mean:.... But trying to do sudo apt-get install snapd says that it is already the latest version.










      share|improve this question














      Trying to setup Heroku CLI to work with WSL.



      Starting by following the directions here for Ubuntu 16+:



      https://devcenter.heroku.com/articles/heroku-cli



      sudo snap install --classic heroku



      Produces the following error:




      error: cannot communicate with server: Post http://localhost/v2/snaps/heroku: dial unix /run/snapd.socket: connect: no such file or directory




      Googled the error and came across this thread:



      https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1631514



      I tried systemctl status snapd.service, which just says the following:




      System has not been booted with systemd as init system (PID 1). Can't operate.




      Restart WSL and the computer and same issue.



      Thought maybe snapd wasn't installed because typing snap or snapd says Command '____' not found, did you mean:.... But trying to do sudo apt-get install snapd says that it is already the latest version.







      windows windows-10 windows-subsystem-for-linux heroku






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 6 at 17:50









      sockpuppetsockpuppet

      1204




      1204






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Nope, doesn't sound like there is current support in WSL for snap. snapd, nor systemd. Thankfully there is a manual install provided by Heroku, so will give that a shot.



          This worked in my case:



          curl https://cli-assets.heroku.com/install.sh | sh






          share|improve this answer





















          • 1





            Do note that sudo applies to individual commands, not to the whole pipeline. curl | sudo sh makes sense (if a bit dangerous), sudo curl | sh is useless.

            – grawity
            Jan 6 at 18:10











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          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%2fsuperuser.com%2fquestions%2f1391219%2fsetting-up-heroku-cli-in-wsl%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














          Nope, doesn't sound like there is current support in WSL for snap. snapd, nor systemd. Thankfully there is a manual install provided by Heroku, so will give that a shot.



          This worked in my case:



          curl https://cli-assets.heroku.com/install.sh | sh






          share|improve this answer





















          • 1





            Do note that sudo applies to individual commands, not to the whole pipeline. curl | sudo sh makes sense (if a bit dangerous), sudo curl | sh is useless.

            – grawity
            Jan 6 at 18:10
















          0














          Nope, doesn't sound like there is current support in WSL for snap. snapd, nor systemd. Thankfully there is a manual install provided by Heroku, so will give that a shot.



          This worked in my case:



          curl https://cli-assets.heroku.com/install.sh | sh






          share|improve this answer





















          • 1





            Do note that sudo applies to individual commands, not to the whole pipeline. curl | sudo sh makes sense (if a bit dangerous), sudo curl | sh is useless.

            – grawity
            Jan 6 at 18:10














          0












          0








          0







          Nope, doesn't sound like there is current support in WSL for snap. snapd, nor systemd. Thankfully there is a manual install provided by Heroku, so will give that a shot.



          This worked in my case:



          curl https://cli-assets.heroku.com/install.sh | sh






          share|improve this answer















          Nope, doesn't sound like there is current support in WSL for snap. snapd, nor systemd. Thankfully there is a manual install provided by Heroku, so will give that a shot.



          This worked in my case:



          curl https://cli-assets.heroku.com/install.sh | sh







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 23 at 16:03

























          answered Jan 6 at 17:54









          sockpuppetsockpuppet

          1204




          1204








          • 1





            Do note that sudo applies to individual commands, not to the whole pipeline. curl | sudo sh makes sense (if a bit dangerous), sudo curl | sh is useless.

            – grawity
            Jan 6 at 18:10














          • 1





            Do note that sudo applies to individual commands, not to the whole pipeline. curl | sudo sh makes sense (if a bit dangerous), sudo curl | sh is useless.

            – grawity
            Jan 6 at 18:10








          1




          1





          Do note that sudo applies to individual commands, not to the whole pipeline. curl | sudo sh makes sense (if a bit dangerous), sudo curl | sh is useless.

          – grawity
          Jan 6 at 18:10





          Do note that sudo applies to individual commands, not to the whole pipeline. curl | sudo sh makes sense (if a bit dangerous), sudo curl | sh is useless.

          – grawity
          Jan 6 at 18:10


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • 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%2fsuperuser.com%2fquestions%2f1391219%2fsetting-up-heroku-cli-in-wsl%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

          "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

          Alcedinidae

          Origin of the phrase “under your belt”?