Run docker container on Raspberry read-only filesytem












0















as said in the title, I need some help to run a Docker container on a Raspberry Pi that has a read-only filesystem.



My docker container is a simple docker container share on my private repository on Docker-Hub that simply executes some "echo" as ENTRYPOINT condition. It works correctly when it is executed on a Raspberry Pi with read-write permission on the filesystem. It is as simpler as possible to do some test about the possibility to run a Docker container in this situation.



In the /etc/fstab file, I modified the permission as follow:



/boot   vfat    default,ro 0 2
/ ext4 default,noatime,ro 0 1


and after the reboot, the system rebooted with the expected permission.



At this point, I would like to be able to run the container that I have already pull from the repository. The docker run myrepotest fails with the following error:



docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. 
See 'docker run --help'.


System configuration:





  1. Docker version: 18.06.1-ce


  2. Raspberry: Raspberry Pi W Zero


  3. Raspbian: Raspbian Stretch (4.14.79)


Is the problem related to the startup of the system that is not able to run the docker daemon?



Is there anyone that can help me to find a solution on running a system daemon with a read-only filesystem?










share|improve this question



























    0















    as said in the title, I need some help to run a Docker container on a Raspberry Pi that has a read-only filesystem.



    My docker container is a simple docker container share on my private repository on Docker-Hub that simply executes some "echo" as ENTRYPOINT condition. It works correctly when it is executed on a Raspberry Pi with read-write permission on the filesystem. It is as simpler as possible to do some test about the possibility to run a Docker container in this situation.



    In the /etc/fstab file, I modified the permission as follow:



    /boot   vfat    default,ro 0 2
    / ext4 default,noatime,ro 0 1


    and after the reboot, the system rebooted with the expected permission.



    At this point, I would like to be able to run the container that I have already pull from the repository. The docker run myrepotest fails with the following error:



    docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. 
    See 'docker run --help'.


    System configuration:





    1. Docker version: 18.06.1-ce


    2. Raspberry: Raspberry Pi W Zero


    3. Raspbian: Raspbian Stretch (4.14.79)


    Is the problem related to the startup of the system that is not able to run the docker daemon?



    Is there anyone that can help me to find a solution on running a system daemon with a read-only filesystem?










    share|improve this question

























      0












      0








      0


      1






      as said in the title, I need some help to run a Docker container on a Raspberry Pi that has a read-only filesystem.



      My docker container is a simple docker container share on my private repository on Docker-Hub that simply executes some "echo" as ENTRYPOINT condition. It works correctly when it is executed on a Raspberry Pi with read-write permission on the filesystem. It is as simpler as possible to do some test about the possibility to run a Docker container in this situation.



      In the /etc/fstab file, I modified the permission as follow:



      /boot   vfat    default,ro 0 2
      / ext4 default,noatime,ro 0 1


      and after the reboot, the system rebooted with the expected permission.



      At this point, I would like to be able to run the container that I have already pull from the repository. The docker run myrepotest fails with the following error:



      docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. 
      See 'docker run --help'.


      System configuration:





      1. Docker version: 18.06.1-ce


      2. Raspberry: Raspberry Pi W Zero


      3. Raspbian: Raspbian Stretch (4.14.79)


      Is the problem related to the startup of the system that is not able to run the docker daemon?



      Is there anyone that can help me to find a solution on running a system daemon with a read-only filesystem?










      share|improve this question














      as said in the title, I need some help to run a Docker container on a Raspberry Pi that has a read-only filesystem.



      My docker container is a simple docker container share on my private repository on Docker-Hub that simply executes some "echo" as ENTRYPOINT condition. It works correctly when it is executed on a Raspberry Pi with read-write permission on the filesystem. It is as simpler as possible to do some test about the possibility to run a Docker container in this situation.



      In the /etc/fstab file, I modified the permission as follow:



      /boot   vfat    default,ro 0 2
      / ext4 default,noatime,ro 0 1


      and after the reboot, the system rebooted with the expected permission.



      At this point, I would like to be able to run the container that I have already pull from the repository. The docker run myrepotest fails with the following error:



      docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. 
      See 'docker run --help'.


      System configuration:





      1. Docker version: 18.06.1-ce


      2. Raspberry: Raspberry Pi W Zero


      3. Raspbian: Raspbian Stretch (4.14.79)


      Is the problem related to the startup of the system that is not able to run the docker daemon?



      Is there anyone that can help me to find a solution on running a system daemon with a read-only filesystem?







      permissions filesystems raspberry-pi docker raspbian






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 14 at 11:54









      AV28AV28

      12




      12






















          0






          active

          oldest

          votes












          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%2f1405668%2frun-docker-container-on-raspberry-read-only-filesytem%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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%2f1405668%2frun-docker-container-on-raspberry-read-only-filesytem%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

          Mouse cursor on multiple screens with different PPI

          Agildo Ribeiro

          Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”