Can't run Docker daemon on Intel Edison

i’m trying to install Docker on my Intel Edison that is running Ubilinux, but need some help.

i compiled the source code using this guide -> https://github.com/docker/docker/blob/master/project/PACKAGERS.md

  • Gunicorn can't find staticfiles after dockerization
  • Docker: Internal UDP communication
  • Two versions of Docker data volumes on same machine?
  • Fail to connect mysql in running wordpress docker
  • Registrator not listening to docker events
  • Single file volume mounted as directory in Docker
  • … but when i try to run the daemon with “./docker daemon” i get this error:

    xotl@ubilinux:~/docker/bundles/1.9.0-dev/binary$ sudo ./docker daemon
    INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
    INFO[0000] [graphdriver] using prior storage driver "aufs"
    INFO[0000] Option DefaultDriver: bridge
    INFO[0000] Option DefaultNetwork: bridge
    INFO[0000] Firewalld running: false
    FATA[0001] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: Failed to program NAT chain: Failed to inject docker in PREROUTING chain: iptables failed: iptables -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER: iptables: No chain/target/match by that name.
     (exit status 1)
    xotl@ubilinux:~/docker/bundles/1.9.0-dev/binary$
    

    Need help. =(

    EDIT:

    This is the output of the sudo iptables -L -v command:

    xotl@ubilinux:~/docker/bundles/1.9.0-dev/binary$ sudo iptables -L -v
    [sudo] password for xotl:
    Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
     pkts bytes target     prot opt in     out     source               destination                            
    
    Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
     pkts bytes target     prot opt in     out     source               destination                            
        0     0 ACCEPT     all  --  any    docker0  anywhere             anywhere                                        ctstate RELATED,ESTABLISHED
        0     0 ACCEPT     all  --  docker0 !docker0  anywhere             anywhere                            
        0     0 ACCEPT     all  --  docker0 docker0  anywhere             anywhere                             
    
    Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
     pkts bytes target     prot opt in     out     source               destination                            
    
    Chain DOCKER (0 references)
     pkts bytes target     prot opt in     out     source               destination
    
    xotl@ubilinux:~/docker/bundles/1.9.0-dev/binary$
    

    This is the output of the sudo iptables -L -v -t natcommand:

    xotl@El-Edison:~/docker/bundles/1.9.0-dev/binary$ sudo iptables -L -v -t nat
    [sudo] password for xotl:
    Chain PREROUTING (policy ACCEPT 4 packets, 1312 bytes)
     pkts bytes target     prot opt in     out     source               destination 
    
    Chain INPUT (policy ACCEPT 4 packets, 1312 bytes)
     pkts bytes target     prot opt in     out     source               destination 
    
    Chain OUTPUT (policy ACCEPT 65 packets, 4940 bytes)
     pkts bytes target     prot opt in     out     source               destination 
    
    Chain POSTROUTING (policy ACCEPT 65 packets, 4940 bytes)
     pkts bytes target     prot opt in     out     source               destination 
    0     0 MASQUERADE  all  --  any    !wlan0  10.10.0.0/21         anywhere   
    
    Chain DOCKER (0 references)
     pkts bytes target     prot opt in     out     source               destination 
    

  • Docker Consul service ip advertised as internal docker ip
  • RHEL7: How to solve “ import read failed(2)”?
  • Kuberntes master not starting up in OpenStack heat
  • Network configuration docker PHP API
  • Kubernetes cluster attempts endless gcr.io DNS lookups, swamping the router. What is wrong and how can I put a stop to it?
  • Can docker use host filesystem instead of an image?
  • One Solution collect form web for “Can't run Docker daemon on Intel Edison”

    Docker requires a 64-bit version of your Operating system (https://docs.docker.com/engine/installation/ubuntulinux/). The Intel Edison runs a 32-bit processor and will not be able to run Docker (at least, that’s what I found after spending some time researching this.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.