• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Register
  • Login
ModalAI Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
    • Register
    • Login

    Docker daemon fails to start on voxl

    Software Development
    11
    40
    6.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      Chad Sweet ModalAI Team
      last edited by 13 May 2021, 15:59

      Not really sure what state your system is in. This github issue shows it could be related to disk space or needs a reboot. Did you install other Dockers on the image? They are very large and maybe all of the space is consumed
      https://github.com/docker/for-linux/issues/435

      1 Reply Last reply Reply Quote 0
      • K
        kiprock
        last edited by 13 May 2021, 16:04

        Just looking at your script, I realized that modal has it's own docker services.. so perhaps this provides a little more info: I have created a few images from the kinetic image

        yocto:~# systemctl disable docker.service
        yocto:~# systemctl enable docker-start.service
        yocto:~# systemctl enable docker-prepare.service
        yocto:~# systemctl status docker-prepare.service
        ● docker-prepare.service
           Loaded: loaded (/etc/systemd/system/docker-prepare.service; enabled; vendor preset: enabled)
           Active: failed (Result: exit-code) since Thu 1970-01-01 00:00:24 UTC; 51 years 4 months ago
         Main PID: 2352 (code=exited, status=1/FAILURE)
        
        Jan 01 00:00:20 apq8096 docker-prepare.sh[2352]: /usr/bin/docker-prepare.sh: line 17: /sys/fs/cgroup/cpuset/syst...ctory
        Jan 01 00:00:21 apq8096 docker-prepare.sh[2352]: /usr/bin/docker-prepare.sh: line 17: /sys/fs/cgroup/cpuset/syst...ctory
        Jan 01 00:00:22 apq8096 docker-prepare.sh[2352]: /usr/bin/docker-prepare.sh: line 17: /sys/fs/cgroup/cpuset/syst...ctory
        Jan 01 00:00:23 apq8096 docker-prepare.sh[2352]: /usr/bin/docker-prepare.sh: line 17: /sys/fs/cgroup/cpuset/syst...ctory
        Jan 01 00:00:24 apq8096 docker-prepare.sh[2352]: /usr/bin/docker-prepare.sh: line 17: /sys/fs/cgroup/cpuset/syst...ctory
        Jan 01 00:00:24 apq8096 docker-prepare.sh[2352]: failed to see cpuset appear after 15 seconds
        Jan 01 00:00:24 apq8096 systemd[1]: docker-prepare.service: Main process exited, code=exited, status=1/FAILURE
        Jan 01 00:00:24 apq8096 systemd[1]: Failed to start docker-prepare.service.
        Jan 01 00:00:24 apq8096 systemd[1]: docker-prepare.service: Unit entered failed state.
        Jan 01 00:00:24 apq8096 systemd[1]: docker-prepare.service: Failed with result 'exit-code'.
        Hint: Some lines were ellipsized, use -l to show in full.
        yocto:~#
        yocto:~#
        yocto:~# systemctl status docker-start.service
        ● docker-start.service
           Loaded: loaded (/etc/systemd/system/docker-start.service; enabled; vendor preset: enabled)
           Active: failed (Result: exit-code) since Thu 2021-05-13 15:57:11 UTC; 3min 11s ago
         Main PID: 3873 (code=exited, status=1/FAILURE)
        
        May 13 15:57:11 apq8096 systemd[1]: Started docker-start.service.
        May 13 15:57:11 apq8096 docker[3873]: time="2021-05-13T15:57:11.453820000Z" level=info msg="API listen on /var/....sock"
        May 13 15:57:11 apq8096 docker[3873]: time="2021-05-13T15:57:11.477567000Z" level=info msg="[graphdriver] using...lay\""
        May 13 15:57:11 apq8096 docker[3873]: time="2021-05-13T15:57:11.527540000Z" level=info msg="Firewalld running: false"
        May 13 15:57:11 apq8096 docker[3873]: time="2021-05-13T15:57:11.595538000Z" level=fatal msg="Error starting dae...oints"
        May 13 15:57:11 apq8096 systemd[1]: docker-start.service: Main process exited, code=exited, status=1/FAILURE
        May 13 15:57:11 apq8096 systemd[1]: docker-start.service: Unit entered failed state.
        May 13 15:57:11 apq8096 systemd[1]: docker-start.service: Failed with result 'exit-code'.
        Hint: Some lines were ellipsized, use -l to show in full.
        yocto:~#
        yocto:~# df
        Filesystem     1K-blocks    Used Available Use% Mounted on
        /dev/root        2837860 1890496    930980  68% /
        devtmpfs         1861956       0   1861956   0% /dev
        tmpfs            1930660       0   1930660   0% /dev/shm
        tmpfs            1930660   17136   1913524   1% /run
        tmpfs            1930660       0   1930660   0% /sys/fs/cgroup
        tmpfs            1930660       4   1930656   1% /var/volatile
        /dev/sda2           2168      80      1964   4% /persist
        /dev/sde12         12016    4184      7508  36% /dsp
        /dev/sda3          58888      40     57568   1% /cache
        /dev/sde11         97232   33616     63616  35% /firmware
        /dev/sda9       15248568 7060916   8171268  47% /data
        tmpfs             386132       0    386132   0% /run/user/0
        
        1 Reply Last reply Reply Quote 0
        • K
          kiprock
          last edited by 13 May 2021, 16:06

          I had a battery go pretty low and the system crashed while running mavros in docker last night, after reboot, docker deamon is not responding and I cannot see any images.

          1 Reply Last reply Reply Quote 0
          • E
            Eric Katzfey ModalAI Team
            last edited by 13 May 2021, 16:39

            @kiprock I would reflash the system, setup your IP connection, configure Docker and just verify that it works as expected.

            1 Reply Last reply Reply Quote 0
            • K
              kiprock
              last edited by 13 May 2021, 16:48

              just looking at the logs, the docker deamon fails here:

              level=fatal msg="Error starting daemon: Error initializing network controller: could not delete the default bridge network: network bridge has active endpoints"
              

              Most forums suggest removing the docker network folder: rm -r /var/lib/docker/network

              I did this but still having issues. Just curious if the modalAI setup stores docker files somewhere else?

              1 Reply Last reply Reply Quote 0
              • E
                Eric Katzfey ModalAI Team
                last edited by 13 May 2021, 16:51

                @kiprock Everything is stored on /data. But again, I would reflash and start over just to verify Docker operation.

                1 Reply Last reply Reply Quote 0
                • K
                  kiprock
                  last edited by 13 May 2021, 16:56

                  rm /data/network/files/local-kv.db
                  

                  did the trick. Thanks for providing that missing piece of data!

                  L 1 Reply Last reply 16 Jun 2022, 14:22 Reply Quote 2
                  • S
                    shlee853 @kiprock
                    last edited by 10 Jun 2021, 20:49

                    @kiprock Hi I have a exactly same issue.

                    I flashed image and reset factory configuration on my VOXL, but, It has still issue.

                    Did you resolve this problem?

                    Thanks,

                    1 Reply Last reply Reply Quote 0
                    • K
                      kiprock
                      last edited by 11 Jun 2021, 16:44

                      @Eric-Katzfey if you cannot start docker images, you can try the command above to clear them. Good luck.

                      E S 2 Replies Last reply 11 Jun 2021, 20:16 Reply Quote 0
                      • E
                        Eric Katzfey ModalAI Team @kiprock
                        last edited by 11 Jun 2021, 20:16

                        Thanks, but I think you meant to ping @shlee853

                        1 Reply Last reply Reply Quote 0
                        • S
                          shlee853 @kiprock
                          last edited by 12 Jun 2021, 00:12

                          @kiprock thank you for your reply
                          I’ll try it

                          S 1 Reply Last reply 12 Jun 2021, 05:17 Reply Quote 0
                          • S
                            shlee853 @shlee853
                            last edited by 12 Jun 2021, 05:17

                            @shlee853

                            Great!

                            I resolved this problem as you mentioned.

                            yocto:/$ rm /data/network/files/local-kv.db
                            yocto:/$ voxl-configure-docker-support.sh 
                            Stopping original docker service
                            Enabling our own services docker-start & docker-prepare
                            starting docker-start.service
                            loading hello-world docker image
                            successfully loaded hello-world
                            starting docker-prepare service
                            Created symlink from /etc/systemd/system/default.target.wants/docker-autorun.service to /etc/systemd/system/docker-autorun.service.
                            
                            done configuring voxl-docker-support
                            
                            1 Reply Last reply Reply Quote 2
                            • L
                              LucasW @kiprock
                              last edited by 16 Jun 2022, 14:22

                              @kiprock Thank you for this, that also solved the issue in my case.

                              To be a little more cautious, I simply renamed the existing file, which forced the generation of a new one when running the configuration script voxl-configure-docker-support.sh:

                              voxl:/data/network/files$ mv local-kv.db local-kv_DISABLED.db
                              
                              1 Reply Last reply Reply Quote 0
                              • José QuintanillaJ
                                José Quintanilla @modaltb
                                last edited by 24 Feb 2023, 19:29

                                @modaltb I have a problem, after I write that line, the drone display a message that says: voxl:/$ voxl-configure-docker-suport.sh
                                bash: voxl-configure-docker-suport.sh: command not found
                                voxl:/$

                                1 Reply Last reply Reply Quote 0
                                • tomT
                                  tom admin
                                  last edited by 24 Feb 2023, 19:42

                                  @José-Quintanilla Looks like you spelled it wrong

                                  1 Reply Last reply Reply Quote 0
                                  • tomT
                                    tom admin
                                    last edited by 24 Feb 2023, 19:42

                                    @José-Quintanilla You can use [TAB] after you start writing a command to auto-fill

                                    José QuintanillaJ 2 Replies Last reply 24 Feb 2023, 19:55 Reply Quote 0
                                    • José QuintanillaJ
                                      José Quintanilla @tom
                                      last edited by 24 Feb 2023, 19:55

                                      @tom I think it worked, thanks

                                      1 Reply Last reply Reply Quote 0
                                      • José QuintanillaJ
                                        José Quintanilla @tom
                                        last edited by José Quintanilla 27 Feb 2023, 17:30 27 Feb 2023, 17:30

                                        @tom It wasn't that, because I need that especific line on my VOXL to work, so I can use properly the sdk

                                        1 Reply Last reply Reply Quote 0
                                        • tomT
                                          tom admin
                                          last edited by 27 Feb 2023, 17:33

                                          @José-Quintanilla What is not working? Did you run voxl-configure-docker-support.sh?

                                          José QuintanillaJ 1 Reply Last reply 27 Feb 2023, 18:20 Reply Quote 0
                                          • José QuintanillaJ
                                            José Quintanilla @tom
                                            last edited by 27 Feb 2023, 18:20

                                            @tom That's the line that doesnt let me run, my done say: voxl-configure-docker-support.sh: command not found

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Powered by NodeBB | Contributors