Get the latest tech news
Running ArchiveTeam's Warrior in Kubernetes
2025-02-04 The "officially endorsed" way of running the ArchiveTeam Warrior project is using one of the available appliance virtual machine images, which keeps itself up to date and "just works". But virtual machines aren't (typically) my preferred method of running applications unless they have some special requirements (like persistant state) - instead I throw containers into my homelab Kubernetes cluster and see what happens.
The "officially endorsed" way of running the ArchiveTeam Warrior project is using one of the available appliance virtual machine images, which keeps itself up to date and "just works". But virtual machines aren't (typically) my preferred method of running applications unless they have some special requirements (like persistant state) - instead I throw containers into my homelab Kubernetes cluster and see what happens. I missed this initially, but it greatly lowers the time it takes to actually start archiving, and removes the web UI in favour of logging to stdout.
Or read this on Hacker News