ARM support

[TomGlass]

Currently the ArchiveTeam Warrior does not support ARM devices.

We're investigating this and looking into building a new image, obviously this requires a lot of work as wget-at (formerly wget-lua) is a complicated setup. We need to validate it and ensure it produces valid content across multiple devices including but not limited to the various Raspberry Pis, Apple M1 architecture and other ARM SBCs such as Orange Pis.

For now we ask anyone working on it please do NOT test anything on live production projects, the risk of garbage data is not one we wish to take. We will begin testing hopefully next week.

For now the current devices we have access to test with are sufficient but may require more later on

[billsargent]

I recommend removing the raspberry pi dockerfiles as well as modifying the README until Arm support is ready.

[TomGlass]

I recommend removing the raspberry pi dockerfiles as well as modifying the README until Arm support is ready.

As it does still work for URLTeam to my knowledge I'll leave it but update readme

[Mechazawa]

What hurdles are there to get it running on ARM64?

[jhollowe]

The main thing is compiling dependencies for arm64, mainly wget-lua and any python packages that do not have wheels built for arm64 (zstandard). Once all software is compiled for arm64, the main functionality of the warrior should be the same as any other platform.

[billsargent]

Can it not be forced to compile things needed to arm32 then until a fix is in place? Can we even pass gcc flags to it?

[TomGlass]

The main thing is compiling dependencies for arm64, mainly wget-lua and any python packages that do not have wheels built for arm64 (zstandard). Once all software is compiled for arm64, the main functionality of the warrior should be the same as any other platform.

It's sadly not that simple. We need to validate wget-at is stable and provides comparable data to amd64. We already are running 2 builds of wget-at due to an issue regarding the reddit project. I have just today finally got an RPI-4 up and I will begin testing next week.

Can it not be forced to compile things needed to arm32 then until a fix is in place? Can we even pass gcc flags to it?

Sadly not.

What hurdles are there to get it running on ARM64?

Highlighted just above.

[Veehxia]

Any news on this ?

[HeroCC]

Just wanted to give my 2 cents here -- it would be incredibly helpful to have a merged manifest with all of the architectures under one tag. This is possible with github actions / docker buildx, but I'm not sure how to do it with Drone's docker plugin. I run a kubernetes cluster with a mix of arm7, arm64, and amd64 boxes, and it would be much better to have one tag, where each box could pull from.

If there's anything you'd like the community to help with please let us know, I'd be happy to help get this up and running :)