Post the output inside a codebox of
dpkg --print-architecture
uname -m
getconf LONG_BIT
Here is the output:
root@medianet:~# dpkg --print-architecture
armhf
root@medianet:~# uname -m
aarch64
root@medianet:~# getconf LONG_BIT
32
root@medianet:~#Does that mean I am running a 32 bit version, so will need a fresh install?
root@medianet:~# dpkg --print-architecture armhf
armhf is 32 bit. So you used a 32-bit image to install debian on the Raspberry before installing OMV. So that's the container error, linuxserver started a few months ago to stop supporting 32-bit architectures in their docker images.
You should reinstall using a 64-bit image if you want to avoid problems like this.
If you reinstall you might want to take a look at this.
You can still use armhf containers but the image need to binded with the last usable armhf TAG.
:armhf-X.Y-123
The TAGs can be seen on the GitHub pages
armhf is 32 bit. So you used a 32-bit image to install debian on the Raspberry before installing OMV. So that's the container error, linuxserver started a few months ago to stop supporting 32-bit architectures in their docker images.
You should reinstall using a 64-bit image if you want to avoid problems like this.
Great, thank you.
When installing OMV originally I followed this guide, where it said to install the 64bit Debian Bullseye Pi OS Lite, so I'm not sure what when wrong.
I'm not sure what when wrong.
You need to flash the 64Bit Lite version:
You need to flash the 64Bit Lite version:
https://downloads.raspberrypi.org/raspios_lite_arm64/images/
Does that mean download the latest image there and choose the "Use custom" option on the Raspberry Pi Imager?
So the Pre-set Raspberry Pi OS 64bit Lite does not work?
Does that mean download the latest image there and choose the "Use custom" option on the Raspberry Pi Imager?
So the Pre-set Raspberry Pi OS 64bit Lite does not work?
I don't know.
This is how I've always done it.
Never used the default on the imager.
You can still use armhf containers but the image need to binded with the last usable armhf TAG.
Are you referring to the last image that linuxserver made for armhf? I'm not sure if doing this is very wise, some of those images could be very outdated. And they will become even more outdated as time goes by.
Are you referring to the last image that linuxserver made for armhf? I'm not sure if doing this is very wise, some of those images could be very outdated. And they will become even more outdated as time goes by.
I know.
All i'm saying is that its possible, not advisable, 
I know.
All i'm saying is that its possible, not advisable,
ok, ok. 
I just wanted to clarify it so that anyone reading this understands it well.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
