You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I also ran into this issue -- it has to deal with arm64 (aka aarch64). (The Dockerfile just specifies Ubuntu 20.04, which will match the host architecture.). As seen in your build log, it fails to build a native ruby extension for ffi, because of the missing system package (libffi-dev). The fallback uses a bundled libffi which is quite ancient and doesn't support arm64:
#7 1.836 /var/lib/gems/2.7.0/gems/ffi-1.9.18/ext/ffi_c/libffi/config.guess: unable to guess system type
#7 1.836 UNAME_MACHINE = aarch64
#7 1.836 UNAME_RELEASE = 5.10.124-linuxkit
#7 1.836 UNAME_SYSTEM = Linux
#7 1.836 UNAME_VERSION = #1 SMP PREEMPT Thu Jun 30 08:18:26 UTC 2022
#7 1.836 configure: error: cannot guess build type; you must specify one
I submitted PR #26 to apt-get install libffi-dev, which solves this immediate issue. (Perhaps this should also use a newer ffi gem as 1.9.18 is quite old, but it at least builds fine when the system libffi is present.)
There are still two remaining issues for arm64 support:
The Dockerfile fetches the linux-x86_64 version of arachni. This doesn't cause the build to fail, but obviously it won't run without adding some Linux equivalent to Rosetta. They don't seem to publish releases for linux-aarch64, so it would need to build from source.
pip install sslyze fails. I think this is just a publishing issue, as they aren't currently publishing a linux-aarch64 wheel for its dependency nassl, but I was able to build it inside this container. I haven't gotten time to file a bug with them yet.
An alternative would be to force using the x86_64 version of Ubuntu, but that would be slower.
I am getting the following error when I clone the repository and run "make build".
I am not sure if it is related but I am using MacOS venture 13.2.1 (22D68) with iTerm2 Build 3.4.19
I searched the web for someone having a similar issue, but looks like I am the first lucky one to get it :)
The text was updated successfully, but these errors were encountered: