Home Assistant Supervised installation not working on BpiM5

I am trying to install Home assistant supervised on BananaPi M5. I have the latest version of Debian 11 Bullseye installed and everything goes to plan however it simply doesn’t start. Ive looked into the journalctl -f and this is the readout but I cannot for the life of me figure out what is causing it to fail. does anyone here have any idea?

> Dec 29 14:09:42 homeassistant hassio-supervisor[7527]: Digest: sha256:8105e126f3bc29f98fa3921b1942c9f31eb3776d2119f6b239a4670cf762251f
> 
> Dec 29 14:09:42 homeassistant hassio-supervisor[7527]: Status: Downloaded newer image for ghcr.io/home-assistant/aarch64-hassio-supervisor:latest
> 
> Dec 29 14:09:42 homeassistant hassio-supervisor[7527]: ghcr.io/home-assistant/aarch64-hassio-supervisor:latest
> 
> Dec 29 14:09:42 homeassistant hassio-supervisor[7468]: [INFO] Creating a new Supervisor container...
> 
> Dec 29 14:09:42 homeassistant systemd[2609]: var-lib-docker-overlay2-721aac5541afda355be9e50d0b05536a0fa963920dccd8b9ee5b7999d6ff1333\x2dinit-merged.mount: Succeeded.
> 
> Dec 29 14:09:42 homeassistant systemd[1]: var-lib-docker-overlay2-721aac5541afda355be9e50d0b05536a0fa963920dccd8b9ee5b7999d6ff1333\x2dinit-merged.mount: Succeeded.
> 
> Dec 29 14:09:42 homeassistant systemd[1]: var-lib-docker-overlay2-721aac5541afda355be9e50d0b05536a0fa963920dccd8b9ee5b7999d6ff1333-merged.mount: Succeeded.
> 
> Dec 29 14:09:42 homeassistant systemd[2609]: var-lib-docker-overlay2-721aac5541afda355be9e50d0b05536a0fa963920dccd8b9ee5b7999d6ff1333-merged.mount: Succeeded.
> 
> Dec 29 14:09:42 homeassistant hassio-supervisor[7712]: e3576e49789e94f7199b43dffb328a73b360bd223dc15011eaef372e788fc859
> 
> Dec 29 14:09:42 homeassistant hassio-supervisor[7468]: [INFO] Starting the Supervisor...
> 
> Dec 29 14:09:42 homeassistant kernel: docker0: port 1(veth3b81e28) entered blocking state
> 
> Dec 29 14:09:42 homeassistant kernel: docker0: port 1(veth3b81e28) entered disabled state
> 
> Dec 29 14:09:42 homeassistant kernel: device veth3b81e28 entered promiscuous mode
> 
> Dec 29 14:09:42 homeassistant kernel: IPv6: ADDRCONF(NETDEV_UP): veth3b81e28: link is not ready
> 
> Dec 29 14:09:42 homeassistant NetworkManager[2172]: <info> [1672322982.8821] manager: (veth79c4dfb): new Veth device (/org/freedesktop/NetworkManager/Devices/34)
> 
> Dec 29 14:09:42 homeassistant systemd-udevd[7719]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
> 
> Dec 29 14:09:42 homeassistant systemd-udevd[7730]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
> 
> Dec 29 14:09:42 homeassistant systemd-udevd[7730]: Using default interface naming scheme 'v247'.
> 
> Dec 29 14:09:42 homeassistant NetworkManager[2172]: <info> [1672322982.8894] manager: (veth3b81e28): new Veth device (/org/freedesktop/NetworkManager/Devices/35)
> 
> Dec 29 14:09:42 homeassistant systemd-udevd[7719]: Using default interface naming scheme 'v247'.
> 
> Dec 29 14:09:42 homeassistant containerd[2262]: time="2022-12-29T14:09:42.986073672Z" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
> 
> Dec 29 14:09:42 homeassistant containerd[2262]: time="2022-12-29T14:09:42.986286883Z" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
> 
> Dec 29 14:09:42 homeassistant containerd[2262]: time="2022-12-29T14:09:42.986348843Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
> 
> Dec 29 14:09:42 homeassistant containerd[2262]: time="2022-12-29T14:09:42.986891891Z" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/e3576e49789e94f7199b43dffb328a73b360bd223dc15011eaef372e788fc859 pid=7747 runtime=io.containerd.runc.v2
> 
> Dec 29 14:09:43 homeassistant systemd[2609]: run-docker-runtime\x2drunc-moby-e3576e49789e94f7199b43dffb328a73b360bd223dc15011eaef372e788fc859-runc.AdUaCm.mount: Succeeded.
> 
> Dec 29 14:09:43 homeassistant systemd[1]: Started libcontainer container e3576e49789e94f7199b43dffb328a73b360bd223dc15011eaef372e788fc859.
> 
> Dec 29 14:09:43 homeassistant systemd[1]: docker-e3576e49789e94f7199b43dffb328a73b360bd223dc15011eaef372e788fc859.scope: Succeeded.
> 
> Dec 29 14:09:43 homeassistant containerd[2262]: time="2022-12-29T14:09:43.267552859Z" level=info msg="shim disconnected" id=e3576e49789e94f7199b43dffb328a73b360bd223dc15011eaef372e788fc859
> 
> Dec 29 14:09:43 homeassistant containerd[2262]: time="2022-12-29T14:09:43.267740361Z" level=warning msg="cleaning up after shim disconnected" id=e3576e49789e94f7199b43dffb328a73b360bd223dc15011eaef372e788fc859 namespace=moby
> 
> Dec 29 14:09:43 homeassistant containerd[2262]: time="2022-12-29T14:09:43.267797487Z" level=info msg="cleaning up dead shim"
> 
> Dec 29 14:09:43 homeassistant containerd[2262]: time="2022-12-29T14:09:43.288960806Z" level=warning msg="cleanup warnings time=\"2022-12-29T14:09:43Z\" level=info msg=\"starting signal loop\" namespace=moby pid=7780 runtime=io.containerd.runc.v2\ntime=\"2022-12-29T14:09:43Z\" level=warning msg=\"failed to read init pid file\" error=\"open /run/containerd/io.containerd.runtime.v2.task/moby/e3576e49789e94f7199b43dffb328a73b360bd223dc15011eaef372e788fc859/init.pid: no such file or directory\" runtime=io.containerd.runc.v2\n"
> 
> Dec 29 14:09:43 homeassistant containerd[2262]: time="2022-12-29T14:09:43.289910943Z" level=error msg="copy shim log" error="read /proc/self/fd/11: file already closed"
> 
> Dec 29 14:09:43 homeassistant dockerd[2275]: time="2022-12-29T14:09:43.290969165Z" level=error msg="stream copy error: reading from a closed fifo"
> 
> Dec 29 14:09:43 homeassistant dockerd[2275]: time="2022-12-29T14:09:43.291190501Z" level=error msg="stream copy error: reading from a closed fifo"
> 
> Dec 29 14:09:43 homeassistant kernel: docker0: port 1(veth3b81e28) entered disabled state
> 
> Dec 29 14:09:43 homeassistant kernel: device veth3b81e28 left promiscuous mode
> 
> Dec 29 14:09:43 homeassistant kernel: docker0: port 1(veth3b81e28) entered disabled state
> 
> Dec 29 14:09:43 homeassistant NetworkManager[2172]: <info> [1672322983.3515] device (veth3b81e28): released from master device docker0
> 
> Dec 29 14:09:43 homeassistant systemd[2609]: var-lib-docker-overlay2-721aac5541afda355be9e50d0b05536a0fa963920dccd8b9ee5b7999d6ff1333-merged.mount: Succeeded.
> 
> Dec 29 14:09:43 homeassistant systemd[1]: var-lib-docker-overlay2-721aac5541afda355be9e50d0b05536a0fa963920dccd8b9ee5b7999d6ff1333-merged.mount: Succeeded.
> 
> Dec 29 14:09:43 homeassistant dockerd[2275]: time="2022-12-29T14:09:43.394864817Z" level=error msg="e3576e49789e94f7199b43dffb328a73b360bd223dc15011eaef372e788fc859 cleanup: failed to delete container from containerd: no such container"
> 
> Dec 29 14:09:43 homeassistant dockerd[2275]: time="2022-12-29T14:09:43.394975694Z" level=error msg="Handler for POST /v1.41/containers/hassio_supervisor/start returned error: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: bpf_prog_query(BPF_CGROUP_DEVICE) failed: invalid argument: unknown"
> 
> Dec 29 14:09:43 homeassistant hassio-supervisor[7722]: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: bpf_prog_query(BPF_CGROUP_DEVICE) failed: invalid argument: unknown
> 
> Dec 29 14:09:43 homeassistant hassio-supervisor[7722]: Error: failed to start containers: hassio_supervisor
> 
> Dec 29 14:09:43 homeassistant systemd[1]: hassio-supervisor.service: Main process exited, code=exited, status=1/FAILURE
> 
> Dec 29 14:09:43 homeassistant systemd[1]: hassio-supervisor.service: Failed with result 'exit-code'.

any insight would be appreciated.