Add-on doesn't work

[davbebawy]

The add-on is poorly made, with the default template "example" all there. When I try to start it after install, all I get is

[FATAL tini (8)] exec /app/api failed: Exec format error
[FATAL tini (7)] exec /app/api failed: Exec format error

@jscarrott @tankerkiller125

[tankerkiller125]

Based on that error the wrong image was installed for your architecture. What's the CPU architecture for your Homebox installation? Our docker image only supports ARM64, AMD64 and ARMv7, so if your using 32 bit or something this won't work on said system.

Edit: Further investigating it looks like the HA specific image is ARM64 only, so some work needs to be sorted there.

[davbebawy]

I am using amd64 with Home Assistant OS.

I noticed in Portainer that all the other image tags are ghcr.io/../amd64:version# so I don't know if that has to be set up in the main repo while building and publishing the images?

[jscarrott]

I might get a chance to look at this tonight, I've had very little spare time recently. I've been meaning to update the add on to the latest homebox version and strip out the last example text.

I know at least one person runs this on amd64 although my instance of ha is arm64, so I'm not sure what has gone wrong for you.

Just FYI opening an issue with something unconstructive like "this is poor quality" and then tagging maintainers isn't very good OSS etiquette. We don't work for you, and I can't speak for tankerkiller but it hardly fills me with enthusiasm to help you.

[jscarrott]

So this was caused by a change made when the addon was moved to sysdminmedia HA addons by convention use a different repo per arch, instead of having multiple tags with different arches under a single repo. The build was moved to just a single repo as tankerkiller said with just aarch64. I could change the build to produce the other arches to separate repos but assume there was a reason to go down to a single repo?

[tankerkiller125]

I'm not sure why that's an HA convention, it makes zero sense to do it that way, in fact it doesn't even make sense to tag them separately given that docker can in fact build multi-arch tags (as we do for Homebox itself). Is this some weird limitation of Homebox itself or something?

[jscarrott]

Looks like it was due to poor multi arch support in the early days of addons (several years ago) but they are looking to move back to just using standard multi arch images now they are the norm.

[jscarrott]

I'll see if I can apply some brain power to work out how to configure the add on builder to stick them all on the same tag.

[tankerkiller125]

@jscarrott the homebox build process itself is probably a good start

[fkrivsky]

Hi guys, have you had any luck with this yet?