Docker Build, Change config to be read from env variables, and pip requirements

[ned-kelly]

Add support for:

• Docker containers,
• Mqtt base prefix,
• Environment variables for config (rather than having to edit the code),
• Pip requirements

[lolouk44]

Thanks. Just back from holidays, will have a look and test...

[lolouk44]

Hi @ned-kelly,
Finally got some time to review your PR.
Please note this is the first time I get a PR so still learning the ropes with this.
First of all, THANKS for your contribution.
I've tried to run the docker with docker-compose but get error messages:

mi-scale    | standard_init_linux.go:190: exec user process caused "no such file or directory"

Any idea where this could come from? I've tried on Ubuntu 16.04

[ned-kelly]

Any idea where this could come from? I've tried on Ubuntu 16.04

Hi @lolouk44

standard_init_linux.go:190 generally means the binary can't be found (inside the container) -- so chances are the CMD or ENTRYPOINT file is not where is should be in the container, OR you're trying to run a custom command that's not installed in the container...

What happens if you run:

docker run --rm -it --privileged mi-scale_mi-scale bash

Do you get the terminal, or do you see the same error?

---

Also in another note, I noticed you pushed the image up to your Docker Hub -- Could I suggest you add arguments to build for armv6 and armv7 so users can run your image on the raspberry/orange pi architectures also - not just a regular x86_64 pc.

Have an awesome weekend!

[lolouk44]

Thanks. The errors were due to Windows CRLF vs LF in ubuntu. I've fixed that by converting the files using dos2unix on both files in src folder. I'll look into the additional arch docker stuff tomorrow. Thanks mate

…

On Sun, 15 Sep 2019 at 00:51, ned-kelly ***@***.***> wrote: Any idea where this could come from? I've tried on Ubuntu 16.04 Hi @lolouk44 <https://github.com/lolouk44> standard_init_linux.go:190 generally means the binary can't be found (inside the container) -- so chances are the CMD or ENTRYPOINT file is not where is should be in the container, OR you're trying to run a custom command that's not installed in the container... What happens if you run: docker run --rm -it --privileged mi-scale_mi-scale bash Do you get the terminal, or do you see the same error? ------------------------------ Also in another note, I noticed you pushed the image up to your Docker Hub -- Could I suggest you add arguments to build for armv6 and armv7 <https://developer.ibm.com/linuxonpower/2017/07/27/create-multi-architecture-docker-image/#targetText=An%20individual%20manifest%20describes%20the,you%20group%20multiple%20images%20together.&targetText=When%20a%20user%20does%20a,on%20which%20it%20is%20running.>so users can run your image on the raspberry/orange pi architectures also - not just a regular x86_64 pc. Have an awesome weekend! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=ABDABYULYIOU5HCH5T4JKCDQJV2JBA5CNFSM4ISZJN62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6XGF6Q#issuecomment-531522298>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABDABYUT4L2GXMHVSBBQSNLQJV2JBANCNFSM4ISZJN6Q> .

[lolouk44]

Think i've just managed to add at least an armv7 to my container.
Just did a git clone on a spare Pi3 and built the docker with :armv7 tag
then pulled the armv7 do my main server and created the manifest.
Would you be able to test to see if I screwed up?

[ned-kelly]

Looking at your tags on docker hub I'm pretty sure you're ok -- Users now just need to 'pull' the image, rather than build it on the device (which is a good thing since it's much quicker to just pull the pre-built image than build on the device).

Unfortunately I can't test ARMv7, however if you do a ARMv6 build (Pi 1, model A & B) I'll test it as I'm running it on a Pi v1 - (and change my current setup to use your image) :)

[lolouk44]

Thanks mate.
I so far haven't figured out how to build a container with a different architecture target so haven't managed to create a container with armv6 as target. (I have an old Pi1 but got some issues there)
Do you by chance have pointers to help me build a container for armv6?
Had a quick look online but see lots of different options that somewhat contradict each other...
Thanks again

[lolouk44]

Any idea why the command RUN apk update would return a non-zero code: 139?
I tried to break the first RUN statement into multiple RUN commands. I always get the same above error message while running on my Pi 1.
Wondering if this is a memory issue, hence wanting to build on my Ubuntu machine with armv6 as target.... Anyway, going to bed now. Good morning to you ;)

[ned-kelly]

Hi @lolouk44 - Shouldn't be any issues manually building the container on a pi1 - HOWEVER you may find that your network adapter is too slow if you're trying to build over wifi and not with an ethernet pugged in, and that can cause all sorts of issues (including timeouts) -- That was my problem at least when trying to build it, and I couldn't be bothered running an ethernet cable to where my PI's located...

The easiest thing to do is build the image locally on your pc (but in an emulated armv6 environment) then copy the built files onto the pi ....

If you do end up building multi-arch images (like on the blog post linked) then you can just tag and push those images up to Dockerhub with a Manifest file, and you're done - You'll have multi-arch support for the miscale images :)

The other option (if you're like me and you never update your software chances are you may be running an old docker without docker buildx support), is to just copy the large files onto the device manually using Docker save, and then do your build (This is actually what I did for the version of miscale that I'm running right now on my PI)...

For example:

Host with reliable Internet

docker pull arm32v6/python:3.8-rc-alpine
docker save -o python3.arm.docker 2a5bd28ae19c
rsync -av python3.arm.docker user@pi-ip:/opt/docker/ #NB Omit the -z flag, no point compressing the file since the CPU is so slow anyway

On your pi

sudo docker load -i python3.arm.docker

vi Dockerfile

## Edit your dockerfile like so:

Replace: FROM python:3.8-rc-alpine
With: FROM 2a5bd28ae19c

Then you can just do a docker build/docker-compose up.

Last thing to note, is that Docker for the piv1 is pretty crappy in Raspbian -- You're better running Hypriotos on the earlier PI's - and putting EVERYTHING in a docker container (makes it easier to rebuild when your SD fails anyway ;) )

https://blog.hypriot.com/downloads/

[lolouk44]

Thanks for all your help mate. Think I've just done it. If you don't mind trying and confirming please.

[ned-kelly]

Hi @lolouk44,

Still not quite there...

You need to include the TAGS for each arch in your docker repo --- Have a look at the tags for the different arch's on another project i've built as an example...

I have a shell script to do the work on my CI/CD server, but you can adapt it for this project also if you like...

Example: setup-multi-arch-build.sh.zip

[lolouk44]

Thanks. Will look into your links, though I thought using docker desktop buildx allowed everything to be under the same latest tag?

[lolouk44]

Took me a while but I think I managed to create the multi-arch tag.
Thanks ever so much for your help.