V2 plugin does not run on ARM

[deminngi]

What you expected to happen?

After executing docker plugin list change of state from ENABLED=false to ENABLED=true
$ docker plugin list
NAME                                         DESCRIPTION                   ENABLED
store/weaveworks/net-plugin:latest_release   Weave Net plugin for Docker   false

What happened?

Error response from daemon: dial unix /run/docker/plugins/a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712/weave.sock: connect: no such file or directory

How to reproduce it?

sudo docker plugin enable --grant-all-permissions store/weaveworks/net-plugin:latest_release

Anything else we need to know?

Running Ubuntu Core 16 on RaspberryPi
$ snap info core

core        16-2.30        3750  canonical   core

Versions:

$ weave version

weave script 2.1.3
weave 2.1.3

$ snap info docker

docker      17.09.1-ce     236   docker-inc  devmode

$ uname -a

Linux rpisvrp0 4.4.0-1080-raspi2 #88-Ubuntu SMP Mon Dec 11 14:23:15 UTC 2017 armv7l armv7l armv7l GNU/Linux

Logs:

$ docker logs weave
n.a.

$ journalctl  -xe -u snap.dockerd.docker.service
- level=debug msg="libcontainerd: received containerd event: &types.Event{Type:\"start-container\", Id:\"a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712\", Status:0x0, Pid:\"\", Timestamp:(*timestamp.Timestamp)(0x5839ab10)}"
- level=debug msg="plugin state changed a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712 libcontainerd.StateInfo{CommonStateInfo:libcontainerd.CommonStateInfo{State:\"start-container\", Pid:0x7fb3, ExitCode:0x0, ProcessID:\"\"}, OOMKilled:false}"
- level=debug msg="libcontainerd: event unhandled: type:\"start-container\" id:\"a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712\" timestamp:<seconds:1516078284 nanos:809165723 > "
- level=debug msg="containerd: process exited" id=a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712 pid=init status=1 systemPid=32691
- level=debug msg="libcontainerd: received containerd event: &types.Event{Type:\"exit\", Id:\"a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712\", Status:0x1, Pid:\"init\", Timestamp:(*timestamp.Timestamp)(0x57ea5420)}"
- level=debug msg="plugin state changed a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712 libcontainerd.StateInfo{CommonStateInfo:libcontainerd.CommonStateInfo{State:\"exit\", Pid:0x0, ExitCode:0x1, ProcessID:\"\"}, OOMKilled:false}"
- level=info msg="standard_init_linux.go:185: exec user process caused \"exec format error\"" plugin=a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712
- level=debug msg="libcontainerd: received containerd event: &types.Event{Type:\"start-container\", Id:\"a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712\", Status:0x0, Pid:\"\", Timestamp:(*timestamp.Timestamp)(0x57ea5640)}"
- level=debug msg="plugin state changed a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712 libcontainerd.StateInfo{CommonStateInfo:libcontainerd.CommonStateInfo{State:\"start-container\", Pid:0x7fe3, ExitCode:0x0, ProcessID:\"\"}, OOMKilled:false}"
- level=debug msg="libcontainerd: event unhandled: type:\"start-container\" id:\"a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712\" timestamp:<seconds:1516078285 nanos:721383482 > "
- level=debug msg="containerd: process exited" id=a35925f469797fd415d53aa53859b1e50fb5bd9052125d9b7561b13dabeb2712 pid=init status=1 systemPid=32739

[deminngi]

Can 'exec user process caused "exec format error"' mean the plugin does not run on armhf?

[rade]

That seems like a fair guess. I wonder whether the plugin in the store is missing an arm image.

[derit]

same issue, on raspberry pi

[bboreham]

I think we don’t have a process to build the v2 plugin for arm. We cross-compile from Intel for the other builds, but v2 plugin requires a full Docker install of the right arch.

[johny-mnemonic]

@bboreham Would you advise how to build the plugin locally without crosscompiling it?
That could interest people with other architectures, not just arm.
I am trying to run docker swarm on a cluster of RPi's and one of my services would benefit from static IPs, so having Weave net would be nice solution.

[bboreham]

@johny-mnemonic it might just work. Otherwise tweak the makefile where it runs qemu.

https://www.weave.works/docs/net/latest/building/

[johny-mnemonic]

@bboreham Thanks for the link.
I tried to follow the instructions and after changes bellow, I made it to compile, but it doesn't seem to produce net-plugin, just all those binaries and images mentioned here.

Is there a way how to call make, to produce net-plugin as well? I did following changes to make it compile directly for arm, but I was unable to find how to tell make to execute this section.

My changes to Makefile (mostly to evade crosscompiling):

-BUILD_IN_CONTAINER=true
+BUILD_IN_CONTAINER=false

#Line 12
-ARCH?=amd64
+ARCH?=arm

#Line 42
-       WEAVEEXEC_DOCKER_ARCH?=armel
+       WEAVEEXEC_DOCKER_ARCH?=arm32v7

-       ALPINE_BASEIMAGE?=arm32v6/alpine:3.6
+       ALPINE_BASEIMAGE?=alpine

#Line 260
-ifeq ($(ARCH),amd64)
+ifeq ($(ARCH),arm)

[bboreham]

Looks like that section is a dependency of make plugin_publish, or you could run it directly make .net-plugin-arm.uptodate