Can't run latest in docker on rPi 4 w/ bookworm aarch64

[MrButlerTron]

I'm trying to run airconnect in docker on aarch64 Bookworm on rPi4 . This is from my docker-compose file:

  airconnect:
    image: 1activegeek/airconnect:latest
    container_name: airconnect
    network_mode: host
    privileged: true
    restart: unless-stopped

This is the log output:

2024-01-20 19:59:15,679 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2024-01-20 19:59:15,685 INFO supervisord started with pid 178
2024-01-20 19:59:16,689 INFO spawned: 'aircast-linux-aarch64' with pid 179
2024-01-20 19:59:16,695 INFO spawned: 'airupnp-linux-aarch64' with pid 180
2024-01-20 19:59:16,753 INFO exited: airupnp-linux-aarch64 (exit status 1; not expected)
2024-01-20 19:59:17,764 INFO success: aircast-linux-aarch64 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-20 19:59:17,768 INFO spawned: 'airupnp-linux-aarch64' with pid 212
2024-01-20 19:59:17,785 INFO exited: airupnp-linux-aarch64 (exit status 1; not expected)
2024-01-20 19:59:19,794 INFO spawned: 'airupnp-linux-aarch64' with pid 220
2024-01-20 19:59:19,833 INFO exited: airupnp-linux-aarch64 (exit status 1; not expected)
2024-01-20 19:59:22,841 INFO spawned: 'airupnp-linux-aarch64' with pid 228
2024-01-20 19:59:22,858 INFO exited: airupnp-linux-aarch64 (exit status 1; not expected)
2024-01-20 19:59:23,859 INFO gave up: airupnp-linux-aarch64 entered FATAL state, too many start retries too quickly

Am I missing something?

[1activegeek]

That doesn't look like anything is wrong at the outset. Docker should recognize to run the arm64 variant. I'm not sure if there are any other details to see what's going on. May want to try and throw debug mode on so you can get some more verbose outputs.

Also - have you tried running the application manually on the same device? Seen any issues that way before attempting the containerized version?

[MrButlerTron]

I wasn't seeing my devices on iOS or in the Spotify client, so I thought it wasn't working and then with the clients exiting it looked like it was crashing out.

It did start working on its own though, so I guess I'm all set.

[1activegeek]

Got it. I mean honestly, running a native synology app is probably easier anyhow 😆 but if you face any issue again, try debug mode in the container and/or running the code natively and see what kind of outputs happen. Might lend some ideas as to what is different or happening. Also could have just be a weird fluke! Thanks for checking it out.