Closed saterunholy closed 1 year ago
Raspberry is based on the ARM architecture, but this image is compatible with the x86_64 architecture.
I see, there are few Librenms images for ARM architecture.
I think an ARM-image would be a nice addition, but I have to consider maintenance vs. benefit (I am pretty busy most of the time).
The image is currently based on Ubuntu 18.04. The upgrade to 20.04 will be a major change, therefore it might be a good opportunity to explore an ARM-image at the same time.
I intend to move to Ubuntu 20.04 with the next baseimage update, maybe this year.
+1 for an arm build. It'd be nice to try this on a pi in docker.
The latest release is based on Ubuntu 20.04, but I am still researching ways to manage multiarch builds on Docker Hub and testing an ARM image (perhaps a virtual machine).
@saterunholy @kllngtme
Please try the latest-arm32v7
and latest-arm64v8
tags.
@jarischaefer latest-arm32v7 seems to work. I'm able to generate a key with no issues. I did see this come up:
librenms | WARNING: MSPHPSQL is not available on armv7l
I'm having an issue with the database currently. The web address when it is up tells me to Check your log for more details. (librenms.log). There's not much in the log I can distinguish of what the issue is. I do see this: [previous exception] [object] (Doctrine\DBAL\Driver\PDO\Exception(code: 2002): SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: No address associated with hostname at /opt/librenms/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDO/Exception.php:18)
I'm thinking this is all chalked up to a database issue. I'm trying mariadb currently, I'm going to switch to try mysql soon. But this is what I have for now.
By way of feedback - Just installed the latest-arm32v7 on my RPI4 Running well so far - Thanks for creating this build Just testing with a single device at present
I have an issue trying to run it on a Raspberry Pi 4 (Raspbian GNU/Linux 10 (buster), once i try to generate the key i get this error: "standard_init_linux.go:211: exec user process caused "exec format error"