5 ms·
Would love to contribute using my Raspberry Pi, but it not supporting ARM is a bit of a pain (and no easy way around it; I want to download the container, run i
by Yeri 2y ago
Would love to contribute using my Raspberry Pi, but it not supporting ARM is a bit of a pain (and no easy way around it; I want to download the container, run it and done): https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior#Can_I_run_the_Warrior_on_ARM_or_some_other_unusual_architecture https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior#C...?
- theblazehen 2y agoThere are some consistency issues when wget-at is compiled for ARM. You can run in under QEMU user emulation however, and I do that on a couple hosts
- NortySpock 2y agoDo you have a write up or link to a page that describes how to run it under QEMU emulation? I've been wanting to try it / publish a docker-compose file that does it in order to make it easy for Raspberry Pi users to spin up a Warrior...
- theblazehen 2y agoI just used https://github.com/dbhi/qus https://github.com/dbhi/qus to enable it for all docker containers on the system (alternatively you can do the binfmt config manually, eg https://wiki.debian.org/QemuUserEmulation https://wiki.debian.org/QemuUserEmulation) However to have it more tightly integrated, you'd want an arm image at /, mount the original warrior image at /warrior, then you could do something like `qemu-user-amd64 /warrior/bin/chroot /warrior/entrypoint` - Updating all paths as relevant