Please build arm compatible image

[programatt]

We would love to use this project on arm devices without having to do our own custom build. I checked everywhere I could and it doesn't appear you have a publicly available arm build that we can use on a raspberry pi.

[michaelshobbs]

I haven't thought through this enough to be honest but open to seeing a PR.

[mrsimonemms]

If I may suggest, use a manifest image. This way, Docker decides the correct image to deliver based upon the architecture. Docker has updated all of it's own images to use this and it makes life much easier.

I wrote a technical blog post on this https://simonemms.com/2017-12-03/docker-swarm-compatible-multiarch-builds-with-manifest, but there are plenty of tutorials out there on this now

[ermaker]

+1

[dubo-dubon-duponey]

I did build a multi-arch image for my own needs (actually, I'm interested in a downstream, logdna) (for arm6, armv7hf, arm64, amd64).

Just a hack at this point but does demonstrate feasibility.

Changeset is here: https://github.com/dubo-dubon-duponey/docker-gliderlabs-logspout/commit/fdf15b0fc2f983bab2698dcfa292a29194d84a1a

This is leveraging buildx (means you need docker 19.03+), albeit the go binary is being cross-compiled using the go toolchain and NOT qemu.

The main issue with the current state of affairs IMO is that people customizing logspout using the extension model (ONBUILD triggers + build.sh / modules.go) will NOT get multi-arch images themselves without doing their homework as well (see the corresponding logdna changes: https://github.com/logdna/logspout/pull/12)

Something more stream-lined could be achieved, but I can't think of a way to not break compatibility with the current extension mechanism...

Either way, 2 cents. Hope that helps.

[thnk2wn]

Would love this as well for my Raspberry Pi based IoT use case. Currently having to use https://github.com/emdem/raspi-logspout

[nebbles]

This may be addressed now by #512 and/or #514?