Proof-of-concept: multi-arch image

[dubo-dubon-duponey]

Just addressing #11 for my own needs right now.

• this is just a proof-of-concept
• this requires a modified version of the upstream (since the extension model of upstream relies on their binary image)
• for upstream, see changes at https://github.com/dubo-dubon-duponey/docker-gliderlabs-logspout/commit/fdf15b0fc2f983bab2698dcfa292a29194d84a1a

Bottom-line:

• this is very feasible
• the whole extension model of upstream should either be changed or this here should move away from the binary dependency and build upstream from source (which it is already doing btw… just from the source shipped in their container rather than from github…)

Demo multi-arch images are available at:

• https://hub.docker.com/r/dubodubonduponey/logspout/
• https://hub.docker.com/r/dubodubonduponey/gliderlabs-logspout

Signed-off-by: dubo-dubon-duponey dubodubonduponey+github@pm.me

[dubo-dubon-duponey]

Running on arm7hf right now.

[dubo-dubon-duponey]

Clarifying what I said above: unless upstream would change their model, I would suggest moving away from their binary dependency on images, and instead rewrite your build using just (github) source (either submodule or git clone in the dockerfile).

Your multi-arch build pipeline would be MUCH simpler and easier to maintain.

[dubo-dubon-duponey]

Closing for lack of interest.

[cederberg]

See also https://github.com/logdna/logspout/pull/25

[darinspivey]

@dubo-dubon-duponey closing this since it was taken care of in https://github.com/logdna/logspout/pull/25

It should be worth noting that in the future we may want to switch things up and start using buildx, but for now the solution we have works well. Thanks for your contribution.