Received: from authenticated.a-painless.mh.aa.net.uk (painless-a.thn.aa.net.uk [IPv6:2001:8b0:0:62::26]) by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id 1F766224090 for <~alpine/users@lists.alpinelinux.org>; Fri, 25 Jul 2025 08:50:25 +0000 (UTC) Received: from [2001:8b0:f70:546d:7218:35fc:b84f:52a4] (helo=baryte) by painless-a.thn.aa.net.uk with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ufE8G-0002cW-2L for ~alpine/users@lists.alpinelinux.org; Fri, 25 Jul 2025 09:50:25 +0100 Date: Fri, 25 Jul 2025 09:49:29 +0100 From: Maximilian Friedersdorff To: ~alpine/users@lists.alpinelinux.org Subject: Illegal instruction on running vaultwarden on RPI (aarch64) Message-ID: <20250725094929.2abbb421@baryte> X-Mailer: Claws Mail 4.3.1 (GTK 3.24.49; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi All, I'm trying to run vaultwarden (tried 1.33.2-r0 and 1.34.1-r1) on a RaspberryPi 4 (aarch64). This used to work fine, but as of upgrading from alpine 3.21 to 3.22, I get an 'Illegal instruction' error whenever I try to execute the main binary: ``` $ /usr/bin/vaultwarden Illegal instruction ``` I initially thought this might be a packaging bug but I'm certain I used to run successfully the older 1.33.2-r0 prior to recently upgrading to alpine 3.22. Instead then I'm inclined to believe that something else *weird* is going on on this system. Nothing sinister, but I haven't been running alpine long and this was my first attempt at upgrading in place. Maybe I missed a step? I'm fairly sure I followed the regular upgrade instructions, followed by upgrading the kernel and initramfs: https://wiki.alpinelinux.org/wiki/Diskless_Mode#Upgrading_a_diskless_system Does anyone have any thoughts for how to begin to debug this? I would think that building vaultwarden from source might be the way to go initially, but this is a rather resource constrained system. I have in fact tried building it, but even with generous swap space and single threaded building (cargo build -j 1) it gets oomkilled. This whole thing is written in rust of course, I know very little about rust. Maybe this is a glaringly obvious issue to someone else. I would massively appreciate any ideas, sucks to be without your password manager! Thanks Max