Cumulus Support

Ok

So latest Armv8/Arm64 build should be working as 3.22.3 (build: 3214)

basic docker compose file attached - remove the txt extension to use (notice phpMyAdmin is arch specific, this needs changed)
Dockerfile attached - remove txt extension to use
build.sh attached, remove txt extension -- this is what I've been running after dropping multi arch - multiarch was only ever proof of concept, so apologies if you had been using this.
multiarch.sh attached - also remove txt to use

Once we finalize something I'll just zip anything up that's needed, but ideally for most people they should just need the compose file.

So I've never really messed with docker builds before, so this was more educational for me than anything else. Below is the multi arch guide, however I could only almost get it working with the 'hard' way and again I stopped looking into it further and did no testing on the other archs.

https://www.docker.com/blog/multi-arch- ... imple-way/

Cool, I see what you're up to. Have you made many changes to the MXWeather.sh file?

In terms of the build process, I solved this using Github Actions. Not sure if you're familiar, or have access, but it's pretty cool. There are two scripts:

Check for release
This runs daily on a cron schedule and checks the build number on the cumulus repo against a text file in my repo. When it detects a difference it writes the new build number to the text file.

Build and push
This script watches the folder containing the text file in my repo and triggers any time it's updated. The build then creates whatever platforms are specified in the build arguments. When the builds are pushed they're tagged with the build number and latest, the idea being that there's then a history of images so if you want to roll back you can just specify a version tag.

If you want to take a look at how it works my repo is here: https://github.com/hucknz/cumulusmx

The build stuff is under the .github/workflows folder.

I haven't made any changes to mxweather.sh

I really like those github actions, I'm not familiar with them at all, however what you have done seems much more useful than the guides I was trying to follow previously!

Can I ask, have you ever had any permission errors with yours?

Thanks. I had fun learning how to use it and liberally borrowed ideas from others. The main benefit for me is the automation, I can just leave it there running in the background.

When you say permission errors do you mean with the build or in the container itself?

Sorry,

My aim originally was that someone could just copy paste the docker compose details and install cumulus with just that information. However regardless of how I tried, the host would always create the initial container as root.

Have you had that experience or were you able to create it as a non root user?

Do you think we could maybe clone your information into a dedicated cumulus account (for docker hub and github) and hand the keys to an admin so that even if both of us disappear the project could still continue by someone that picks up the mantle?

@admin: would it be interesting to make a separate docker forum somewhere (e.g. in the general/other block)? This does not seem to be a CMX issue and also does not seem to fit anywhere else. But maybe it does fit somewhere in an existing place

I would like to suggest a home automation section - which would contain

Docker/docker compose
home assistant
homebridge
MQTT
node red?
influxDB
possibly more?

That sort of thing, I realise that docker does not fit directly with home automation, however home automation does certainly fit with lots of docker. I do believe most of the above goes hand in hand.

As an example, even though it has taken me 4 months to get there after going down Hans fantastic Cutils path - all I ever wanted was to run CMX, export it to influxDB and then use it within my home assistant setup (btw without you Hans, I couldn't have had cool public graphs and a fantastic site to share with my town, so I would never ask for those 4 months back)- but this is not just my personal request, I genuinely feel there are many people out there that would be looking for something similar, just my two cents.

Arm64 arch updated to Patch release 3.22.4 - build 3215.

My aim originally was that someone could just copy paste the docker compose details and install cumulus with just that information. However regardless of how I tried, the host would always create the initial container as root.

I think this might be one of the downsides of docker, it runs as root. I believe there's an alternative called Podman that is effectively a non-root user but I don't have any experience with it.

With the container being created as root, how does that cause problems?

Do you think we could maybe clone your information into a dedicated cumulus account (for docker hub and github) and hand the keys to an admin so that even if both of us disappear the project could still continue by someone that picks up the mantle?

Happy to contribute to that. I did suggest in my initial comment (on the original thread) that if the Cumulus MX team were interested I'd be happy to contribute to an "official" docker build pipeline under their repo so all of the things can live on if one or both of us has to drop out. Still more than happy to support that effort.

Arm64 arch updated to Patch release 3.22.4 - build 3215.

Cool! I saw there was a new release today, here's hoping the automated process picks that up later today (runs around 7-8pm UTC) and builds as expected.

Looks like the build ran as expected, b3215 is up on docker hub.

hucknz

sorry I'm going to get back into this in the next few days - do you know if usb support works within your environment?

No worries. By usb support you mean being able to connect the display for the station via usb to sync data? If that’s the case then yes. I’m using it with a Fine Offset clone.

the base image that we used had a build for usb and one without usb - I believe with his image it wouldn't boot or would error out if you didn't have usb connected.

Do you know if your image boots without USB? or would it work if you commented it out of the docker-compose file?

I'll be honest, I don't think the creators are interested in setting up an official docker repository - but I'd rather get it off our own personal accounts so that if either of us disappears it can still be maintained. We should setup a separate github for the releases, you and I have admin and keep an admin login that we can give to Freddie or one of the other board admins for the future.

I don’t think there’s any issue running it without the usb pass through, I think that’s how I got it set up originally, but I can try testing it and confirm.

Happy to setup a new repo if that’s easiest. Have you asked the admins if they’d be open to creating one within the main cumulus repo? At least if we ask we get a clear answer either way.

I can confirm the container starts fine without the USB passthrough.