Docker daemon fails to start on voxl



  • RE: https://forum.modalai.com/topic/37/docker-daemon-fails-to-start-voxl
    I'm also facing the same issue.

    yocto:/# voxl-docker -i roskinetic-xenial:opencv
    Cannot connect to the Docker daemon. Is the docker daemon running on this host?
    yocto:/#
    yocto:/#
    yocto:/# docker images
    Cannot connect to the Docker daemon. Is the docker daemon running on this host?
    yocto:/#
    yocto:/#
    yocto:/# df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/root 2.8G 2.2G 581M 79% /
    devtmpfs 1.8G 0 1.8G 0% /dev
    tmpfs 1.9G 0 1.9G 0% /dev/shm
    tmpfs 1.9G 17M 1.9G 1% /run
    tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
    tmpfs 1.9G 4.0K 1.9G 1% /var/volatile
    /dev/mmcblk0p1 7.4G 204M 7.2G 3% /mnt/sdcard
    /dev/sda2 2.2M 80K 2.0M 4% /persist
    /dev/sde12 12M 4.1M 7.4M 36% /dsp
    /dev/sde11 95M 33M 63M 35% /firmware
    /dev/sda3 58M 40K 57M 1% /cache
    /dev/sda9 15G 13G 2.4G 85% /data
    yocto:/#

    As you can see, /data partition has all the data and docker images.

    What can be a solution for this?


  • Dev Team

    What do you see after running voxl-configure-docker.sh ?

    Should be something like:

    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
    
    done configuring voxl-docker-support
    


  • 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
    Cannot connect to the Docker daemon. Is the docker daemon running on this host?
    yocto:/#



  • yocto:/# systemctl status docker
    ā— docker.service - Docker Application Container Engine
    Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Mon 2021-01-11 06:31:53 UTC; 1min 53s ago
    Docs: http://docs.docker.com
    Main PID: 4675 (code=exited, status=2)

    Jan 11 06:31:53 apq8096 systemd[1]: Started Docker Application Container Engine.
    Jan 11 06:31:53 apq8096 docker[4675]: flag provided but not defined: --raw-logs
    Jan 11 06:31:53 apq8096 docker[4675]: See '/usr/bin/docker daemon --help'.
    Jan 11 06:31:53 apq8096 systemd[1]: docker.service: Main process exited, co...NT
    Jan 11 06:31:53 apq8096 systemd[1]: docker.service: Unit entered failed state.
    Jan 11 06:31:53 apq8096 systemd[1]: docker.service: Failed with result 'exi...'.
    Jan 11 06:31:57 apq8096 systemd[1]: Stopped Docker Application Container Engine.
    Jan 11 06:33:06 apq8096 systemd[1]: Stopped Docker Application Container Engine.
    Hint: Some lines were ellipsized, use -l to show in full.



  • This post is deleted!


  • As I'm working on this issue, I noticed the following.

    yocto:/# ifconfig
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:32 errors:0 dropped:0 overruns:0 frame:0
    TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2224 (2.1 KiB) TX bytes:2224 (2.1 KiB)

    wlan0 Link encap:Ethernet HWaddr :::::
    inet addr:192.168..** Bcast:192.168..*** Mask:...
    inet6 addr: ::
    :::**/** Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:467 errors:0 dropped:0 overruns:0 frame:0
    TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:3000
    RX bytes:40293 (39.3 KiB) TX bytes:10317 (10.0 KiB)

    https://stackoverflow.com/questions/64028448/error-during-connect-get-http-2fvar2frun2fdocker-sock-v1-40-containers-jso

    It's not showing any IP address for docker0.
    How to configure the IP address that will listen to docker daemon on voxl-core board?


Log in to reply