ok - image built from 5.17 in Pi3 and node 12.18 runs just fine but image built changing 5.17 to 5.75 in the same dockerfile fails with missing fibers error so something has broken (in my environment at least) between 5.17 and 5.75

Just looked in the repos and I see there is now an offical arm64 dockerfile..... that didn't exist when I began so I created my own, which is the one not working. I can see stuff relating to fibers in official so will give that a go today

@b3lt3r Please try current 5.75 bundle from https://releases.wekan.team/raspi3/ , I made some fixes

arm64 dockerfile has not been tested, I don't know does it work

There is currently Snap and Docker versions only for x64

I have not done arm64/s390x/ppl64le versions yet

I did also make changes to arm64 bundle build scripts https://github.com/wekan/wekan/blob/master/releases/maintainer-make-bundle-a.sh

it does now add fibers correctly

I was originally using the 5.75 bundle from 12/11 and I don't see an update after that. I did try the arm64 dockerfile but that is a qemu based cross compile on amd64. It worked up to a point and then stopped with an invalid exec error which seemed due to trying to run (maybe) arm code on the amd.

What I'll try next is the 5.75 bundle outside of docker but my endgame is always to run in docker as that gives me more isolation. Failing that I'll try the amd64 docker compose with latest and see how that goes.

The dockerfile I have that works fine with 5.17 is very simple - bases on Ubuntu Groovy, adds a few utils for the OS (wget and zip), downloads and unzips Pi3 bundle, installs the node release and adds the start scripts reference which I have outside the docker so I can easily modify if required.

Rgds

Currently Docker and Snap is amd64. I'm now trying to add arm64/s390x/ppc64le

adding is in progress, not ready yet

Great - my 5.17 works fine as is so I'm safe till then :-)

well.... I have gone to the dark side and started migrating all my Pi apps onto an amd64 Debian host so the arm64 issue isn't one for me any more :-) As an aside - is there any exposure to the Log4J vulnerability? I can't imagine there is but definitive confirmation would be great.

@b3lt3r https://github.com/wekan/wekan/issues/4233

You are the 4th that asked about Log4j. When there is no Java code in WeKan at all.

And no Log4j at all.

ok - thank you, good to be certain!

Other Q. My dates all display in American m/d/y format. My browser is set to English (UK), my Linux desktop is set en_gb as is my linux server that the docker runs on. I log in with language English (UK) and always see dates is mm/dd/yyy format.....

WeKan ® Version 5.84.0 Meteor version 2.2 Node version 12.22.7 MongoDB version 4.4.10

I've used a new private browser, cleared cache but still it shows in US date format

ok - just saw an issue on Github referring to mquandallemoment and when I look at my browser inspector I see this message: Loading failed for the <script> with source “http://localhost/packages/mquandalle_moment/locale/en-gb.js?=1640948758484”

so I guess that's the issue... Not a dealbreaker but jarring :-)

@b3lt3r dates depend on language. English is m/d/y, English (UK) is d/m/y. You can select language at right top click your username / Language.

@b3lt3r That language stuff will change to be always set serverside, so it will work always correctly, and there will be selection of any date format.