Issues when running AET on ARM64 architecture using Mac M1 Apple Silicon

[coumarine]

Thanks for detailed and clear steps for running AET instance using Helm.

Tried the steps mentioned in https://wttech.blog/blog/2021/running-aet-using-helm/ Getting below alerts in Docker Dashboard against a few of the docker images;

Also on running "watch -n 1 kubectl get pods,statefulsets --namespace local" getting below i.e. respective images are not in READY state

As a result executing "./aet.sh http://aet-127.0.0.1.nip.io b4c-suite.xml" throws below error; parse error: Invalid numeric literal at line 1, column 10 Unsuccessful Request to "http://aet-127.0.0.1.nip.io/suite", status: 404, error:

Please can you have a look.

[malaskowski]

Hi @coumarine , It looks like you are running your AET on Mac M1, right? This sometimes requires Docker images created in the dedicated architecture. Let me check if I can upgrade current images to support linux/arm64 platform.

[coumarine]

@malaskowski That’s right. I am running AET in Mac.

Would appreciate if you could upgrade the images to support Mac.

[malaskowski]

@coumarine , I managed to release 1.2.0 version for all AET images but Karaf. I was not able to build Karaf image for ARM64 architecture using CI (Ubuntu AMD64) and vice versa - I couldn't build AMD64 on my Mac. I pushed my local ARM64 Karaf version under 1.2.0-arm64 tag. I also released the 0.5.0 version of AET Helm Chart. Please try the following command to run AET locally on your M1 Apple Silicon processor:

helm repo update aet-chart
helm install \
    --timeout 15m \
    --set ingress.enabled=true \
    --set aetDockerTag=1.2.0 \
    --set karaf.image.tag=1.2.0-arm64 \
    --namespace local \
    my-aet aet-chart/aet --create-namespace

For running the production use just 1.2.0 tag (assuming you're running it on Linux AMD64-based nodes).

[coumarine]

@malaskowski many thanks for the updated images.

I have uninstalled my previous helm installation of 'my-aet', and executed the helm update and helm install as mentioned in your above comments.

However getting the same error parse error: Invalid numeric literal at line 1, column 10 Unsuccessful Request to "http://aet-127.0.0.1.nip.io/suite", status: 404, error: while executing "./aet.sh http://aet-127.0.0.1.nip.io/ my-suite.xml" Please can you suggest, if there are any updates required in aet.sh file.

Also not sure if it is due to some of the images still throw alerts;

Below is the result of watch -n 1 kubectl get pods,statefulsets --namespace local

Note: In the past when we used AET Docker version, we have updated the aet-swarm.yml; chrome: image: selenium/node-chrome:3.14.0-arsenic to chrome: image: selenium/node-chrome:latest

Is there a way in AET Helm version, to use the selenium/node-chrome:latest image?

[malaskowski]

@coumarine , I'm no longer AET application maintainer. Commits say nothing has changed in aet.sh for the last 3 years... You may try curl -F "suite=@my-suite.xml" "http://aet-127.0.0.1.nip.io/suite" - triggering AET suite is just a call to its Web API.

Regarding the selenium/node-chrome image, I would not expect it will work with the latest tag. There is a new major version of selenium. AFAIK AET does not support the latest 4.x version of Selenium: https://github.com/wttech/aet/issues/682 (but you may try to ask maintainers for an update :) ).

I don't have good feelings about 3.14.0-arsenic version supporting M1 processors...

Try running AET images in version 1.2.0 in the cloud, it should run without issues on AMD64 architecture. There are many cloud providers with a free trial period and managed Kubernetes cluster (e.g. Digital Ocean, GCP). You can also look at the Karaf pod logs and see what happens inside to identify potential issue.

Cheers

[coumarine]

@malaskowski Many thanks for guiding through. Your help in-spite of you not being the maintainer of AET, is much appreciated.