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

    Docker daemon fails to start on voxl

    Software Development
    11
    40
    5950
    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.
    • Eric KatzfeyE
      Eric Katzfey ModalAI Team
      last edited by

      @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

        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
        • Eric KatzfeyE
          Eric Katzfey ModalAI Team
          last edited by

          @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

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

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

            LucasWL 1 Reply Last reply Reply Quote 2
            • S
              shlee853 @kiprock
              last edited by

              @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

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

                Eric KatzfeyE S 2 Replies Last reply Reply Quote 0
                • Eric KatzfeyE
                  Eric Katzfey ModalAI Team @kiprock
                  last edited by

                  Thanks, but I think you meant to ping @shlee853

                  1 Reply Last reply Reply Quote 0
                  • S
                    shlee853 @kiprock
                    last edited by

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

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      shlee853 @shlee853
                      last edited by

                      @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
                      • LucasWL
                        LucasW @kiprock
                        last edited by

                        @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

                          @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

                            @José-Quintanilla Looks like you spelled it wrong

                            1 Reply Last reply Reply Quote 0
                            • tomT
                              tom admin
                              last edited by

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

                              José QuintanillaJ 2 Replies Last reply Reply Quote 0
                              • José QuintanillaJ
                                José Quintanilla @tom
                                last edited by

                                @tom I think it worked, thanks

                                1 Reply Last reply Reply Quote 0
                                • José QuintanillaJ
                                  José Quintanilla @tom
                                  last edited by José Quintanilla

                                  @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

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

                                    José QuintanillaJ 1 Reply Last reply Reply Quote 0
                                    • José QuintanillaJ
                                      José Quintanilla @tom
                                      last edited by

                                      @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
                                      • tomT
                                        tom admin
                                        last edited by

                                        @José-Quintanilla What release do you have installed, what does voxl-version say?

                                        José QuintanillaJ 1 Reply Last reply Reply Quote 0
                                        • José QuintanillaJ
                                          José Quintanilla @tom
                                          last edited by

                                          @tom If I recall is the 0.9 version

                                          1 Reply Last reply Reply Quote 0
                                          • tomT
                                            tom admin
                                            last edited by

                                            @José-Quintanilla When you get a chance post the output of voxl-version. Also what hardware are you on?

                                            José QuintanillaJ 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Powered by NodeBB | Contributors