docker snap: Cannot connect to the Docker daemon. Is the docker daemon running on this host?












3















I added the docker snap package to my Ubuntu 16.04 machine



sudo snap install docker


Now, when I try to use it, I get the following error...




Cannot connect to the Docker daemon. Is the docker daemon running on this host?











share|improve this question



























    3















    I added the docker snap package to my Ubuntu 16.04 machine



    sudo snap install docker


    Now, when I try to use it, I get the following error...




    Cannot connect to the Docker daemon. Is the docker daemon running on this host?











    share|improve this question

























      3












      3








      3








      I added the docker snap package to my Ubuntu 16.04 machine



      sudo snap install docker


      Now, when I try to use it, I get the following error...




      Cannot connect to the Docker daemon. Is the docker daemon running on this host?











      share|improve this question














      I added the docker snap package to my Ubuntu 16.04 machine



      sudo snap install docker


      Now, when I try to use it, I get the following error...




      Cannot connect to the Docker daemon. Is the docker daemon running on this host?








      snap docker






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 20 '17 at 17:48









      Zachary FieldsZachary Fields

      35229




      35229






















          2 Answers
          2






          active

          oldest

          votes


















          2














          Due to confinement issues in the evolving snappy model, Docker is not full flavored by default (see the discussion on the Snapcraft forum).



          To get some helpful instructions on how to work around (i.e. break) the confinement model until the proper fix is in place. You can simply check the Docker help application packaged in the snap.



          $ docker.help
          Docker snap: Docker Linux container runtime.

          Due to the confinement issues on snappy, it requires some manual setup to make docker-snap works on your machine.
          We'll take you through the steps needed to set up docker snap work for you on ubuntu core and ubuntu classic.

          On Ubuntu classic, before installing the docker snap,
          please run the following command to add the login user into docker group.
          sudo addgroup --system docker
          sudo adduser $USER docker
          newgrp docker

          On Ubuntu Core 16, after installing the docker snap from store,
          Firstly, you need to connect the two interfaces as they're not auto-connected by default.
          sudo snap connect docker:account-control :account-control
          sudo snap connect docker:home :home

          Secondly, reload the snap and allows the user to login to the new group "docker-snap".
          snap disable docker
          snap enable docker
          newgrp docker-snap

          Then have fun with docker in snappy.


          The last command fails...



          $ newgrp docker-snap
          newgrp: group 'docker-snap' does not exist


          However, I did not notice any negative impact based on the failure, and Docker now functions as I would expect.






          share|improve this answer

































            0














            Use snap start docker to activate the service. It might need root permissions.






            share|improve this answer








            New contributor




            Luis 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: "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%2f907110%2fdocker-snap-cannot-connect-to-the-docker-daemon-is-the-docker-daemon-running-o%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









              2














              Due to confinement issues in the evolving snappy model, Docker is not full flavored by default (see the discussion on the Snapcraft forum).



              To get some helpful instructions on how to work around (i.e. break) the confinement model until the proper fix is in place. You can simply check the Docker help application packaged in the snap.



              $ docker.help
              Docker snap: Docker Linux container runtime.

              Due to the confinement issues on snappy, it requires some manual setup to make docker-snap works on your machine.
              We'll take you through the steps needed to set up docker snap work for you on ubuntu core and ubuntu classic.

              On Ubuntu classic, before installing the docker snap,
              please run the following command to add the login user into docker group.
              sudo addgroup --system docker
              sudo adduser $USER docker
              newgrp docker

              On Ubuntu Core 16, after installing the docker snap from store,
              Firstly, you need to connect the two interfaces as they're not auto-connected by default.
              sudo snap connect docker:account-control :account-control
              sudo snap connect docker:home :home

              Secondly, reload the snap and allows the user to login to the new group "docker-snap".
              snap disable docker
              snap enable docker
              newgrp docker-snap

              Then have fun with docker in snappy.


              The last command fails...



              $ newgrp docker-snap
              newgrp: group 'docker-snap' does not exist


              However, I did not notice any negative impact based on the failure, and Docker now functions as I would expect.






              share|improve this answer






























                2














                Due to confinement issues in the evolving snappy model, Docker is not full flavored by default (see the discussion on the Snapcraft forum).



                To get some helpful instructions on how to work around (i.e. break) the confinement model until the proper fix is in place. You can simply check the Docker help application packaged in the snap.



                $ docker.help
                Docker snap: Docker Linux container runtime.

                Due to the confinement issues on snappy, it requires some manual setup to make docker-snap works on your machine.
                We'll take you through the steps needed to set up docker snap work for you on ubuntu core and ubuntu classic.

                On Ubuntu classic, before installing the docker snap,
                please run the following command to add the login user into docker group.
                sudo addgroup --system docker
                sudo adduser $USER docker
                newgrp docker

                On Ubuntu Core 16, after installing the docker snap from store,
                Firstly, you need to connect the two interfaces as they're not auto-connected by default.
                sudo snap connect docker:account-control :account-control
                sudo snap connect docker:home :home

                Secondly, reload the snap and allows the user to login to the new group "docker-snap".
                snap disable docker
                snap enable docker
                newgrp docker-snap

                Then have fun with docker in snappy.


                The last command fails...



                $ newgrp docker-snap
                newgrp: group 'docker-snap' does not exist


                However, I did not notice any negative impact based on the failure, and Docker now functions as I would expect.






                share|improve this answer




























                  2












                  2








                  2







                  Due to confinement issues in the evolving snappy model, Docker is not full flavored by default (see the discussion on the Snapcraft forum).



                  To get some helpful instructions on how to work around (i.e. break) the confinement model until the proper fix is in place. You can simply check the Docker help application packaged in the snap.



                  $ docker.help
                  Docker snap: Docker Linux container runtime.

                  Due to the confinement issues on snappy, it requires some manual setup to make docker-snap works on your machine.
                  We'll take you through the steps needed to set up docker snap work for you on ubuntu core and ubuntu classic.

                  On Ubuntu classic, before installing the docker snap,
                  please run the following command to add the login user into docker group.
                  sudo addgroup --system docker
                  sudo adduser $USER docker
                  newgrp docker

                  On Ubuntu Core 16, after installing the docker snap from store,
                  Firstly, you need to connect the two interfaces as they're not auto-connected by default.
                  sudo snap connect docker:account-control :account-control
                  sudo snap connect docker:home :home

                  Secondly, reload the snap and allows the user to login to the new group "docker-snap".
                  snap disable docker
                  snap enable docker
                  newgrp docker-snap

                  Then have fun with docker in snappy.


                  The last command fails...



                  $ newgrp docker-snap
                  newgrp: group 'docker-snap' does not exist


                  However, I did not notice any negative impact based on the failure, and Docker now functions as I would expect.






                  share|improve this answer















                  Due to confinement issues in the evolving snappy model, Docker is not full flavored by default (see the discussion on the Snapcraft forum).



                  To get some helpful instructions on how to work around (i.e. break) the confinement model until the proper fix is in place. You can simply check the Docker help application packaged in the snap.



                  $ docker.help
                  Docker snap: Docker Linux container runtime.

                  Due to the confinement issues on snappy, it requires some manual setup to make docker-snap works on your machine.
                  We'll take you through the steps needed to set up docker snap work for you on ubuntu core and ubuntu classic.

                  On Ubuntu classic, before installing the docker snap,
                  please run the following command to add the login user into docker group.
                  sudo addgroup --system docker
                  sudo adduser $USER docker
                  newgrp docker

                  On Ubuntu Core 16, after installing the docker snap from store,
                  Firstly, you need to connect the two interfaces as they're not auto-connected by default.
                  sudo snap connect docker:account-control :account-control
                  sudo snap connect docker:home :home

                  Secondly, reload the snap and allows the user to login to the new group "docker-snap".
                  snap disable docker
                  snap enable docker
                  newgrp docker-snap

                  Then have fun with docker in snappy.


                  The last command fails...



                  $ newgrp docker-snap
                  newgrp: group 'docker-snap' does not exist


                  However, I did not notice any negative impact based on the failure, and Docker now functions as I would expect.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Nov 20 '17 at 17:50

























                  answered Apr 20 '17 at 17:48









                  Zachary FieldsZachary Fields

                  35229




                  35229

























                      0














                      Use snap start docker to activate the service. It might need root permissions.






                      share|improve this answer








                      New contributor




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

























                        0














                        Use snap start docker to activate the service. It might need root permissions.






                        share|improve this answer








                        New contributor




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























                          0












                          0








                          0







                          Use snap start docker to activate the service. It might need root permissions.






                          share|improve this answer








                          New contributor




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










                          Use snap start docker to activate the service. It might need root permissions.







                          share|improve this answer








                          New contributor




                          Luis 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




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









                          answered 11 mins ago









                          LuisLuis

                          1




                          1




                          New contributor




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





                          New contributor





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






                          Luis 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 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%2f907110%2fdocker-snap-cannot-connect-to-the-docker-daemon-is-the-docker-daemon-running-o%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

                              GameSpot

                              connect to host localhost port 22: Connection refused

                              Getting a Wifi WPA2 wifi connection