Other Hardware/Boards Blueos has run on

[Williangalvani]

I propose we use this issue for users to report other Hardwares they got BlueOS to run on, and we can regularly transfer them to the docs if we feel we need to.

[Williangalvani]

I'll start!

I got it running on a Radxa Zero 3E .
I used the radxa-zero3_ubuntu_jammy_xfce_b6.img.xz Image as the cli doesn't seem to work.
The default user/pass is rock:rock, so I needed bluerobotics/BlueOS#2998 and these custom settings:

{
    "core": {
        "binds": {
            "/dev/": {
                "bind": "/dev/",
                "mode": "rw"
            },
            "/etc/blueos": {
                "bind": "/etc/blueos",
                "mode": "rw"
            },
            "/etc/dhcpcd.conf": {
                "bind": "/etc/dhcpcd.conf",
                "mode": "rw"
            },
            "/etc/machine-id": {
                "bind": "/etc/machine-id",
                "mode": "ro"
            },
            "/etc/resolv.conf.host": {
                "bind": "/etc/resolv.conf.host",
                "mode": "ro"
            },
            "/home/pi/.ssh": {
                "bind": "/home/pi/.ssh",
                "mode": "rw"
            },
            "/home/rock/.ssh": {
                "bind": "/home/rock/.ssh",
                "mode": "rw"
            },
            "/run/udev": {
                "bind": "/run/udev",
                "mode": "ro"
            },
            "/sys/": {
                "bind": "/sys/",
                "mode": "rw"
            },
            "/tmp/wpa_playground": {
                "bind": "/tmp/wpa_playground",
                "mode": "rw"
            },
            "/usr/blueos/bin": {
                "bind": "/usr/blueos/bin",
                "mode": "rw"
            },
            "/usr/blueos/extensions": {
                "bind": "/usr/blueos/extensions",
                "mode": "rw"
            },
            "/usr/blueos/userdata": {
                "bind": "/usr/blueos/userdata",
                "mode": "rw"
            },
            "/var/logs/blueos": {
                "bind": "/var/logs/blueos",
                "mode": "rw"
            },
            "/var/run/dbus": {
                "bind": "/var/run/dbus",
                "mode": "rw"
            },
            "/var/run/docker.sock": {
                "bind": "/var/run/docker.sock",
                "mode": "rw"
            },
            "/var/run/wpa_supplicant": {
                "bind": "/var/run/wpa_supplicant",
                "mode": "rw"
            }
        },
        "enabled": true,
        "environment": [
            "SSH_USER=rock",
            "SSH_PASSWORD=rock",
            "USER_UID=1001",
            "USER_GID=1001",
            "BLUEOS_DISABLE_SERVICES=wifi,autopilot"
        ],
        "image": "williangalvani/blueos-core",
        "network": "host",
        "privileged": true,
        "tag": "user_pass",
        "webui": false
    }
}

The relevant changes are the environment variables, and the /home mounts.
I additionally disabled the wifi service as this board has no wifi, and the autopilot service as it was going mad without a board detected

[Williangalvani]

CM4:
Needed to be installed with the install script
/etc/wpa_supplicant/wpa_supplicant.conf needs to be added manually (see bluerobotics/BlueOS#3170)