Issues when starting runtipi-queue container
Hi, after an update i had issues with runtipi so decided to migrate to the latest beta to see if that would solve it but still there were problems so decided to fully delete all the docker volumes, images etc including the runtipi folder itself and start fresh. But i keep on facing the same issue of the runtipi-queue container being unhealthy (probably a rabbitmq related issue). I have attached logs.
43 Replies
Docker version 28.1.1, build 4eba377327
Please check here https://discord.com/channels/976934649643294750/1367422351163265106/1367422789019242506
It has instructions on how to solve the issue
works fine now
It's a small bug and we will fix it in the next update
Oh alright, stopping it and starting it again solved the issue.
Thanks, the disk space doesn't display but not a big deal as it probably will be fixed in the next release. (nvm after restarting disk space issue was gone and on 4.0.2 i dont get it anymore).
Invidious also fails to install too.
Are all of your apps up to date?
yep
only invidious fails to install
@Lancelot what do you think?
summoned the appstore guy
Invidious has a specific docker-compose for ARM because image are splitted.
It keeps using
docker-compose.arm64.yml
instead of the generated one.
I believe removing the arm64.yml should prevent this behavior but it will remain an issue since the default image won't fit for an ARM machine.Will it require modifying the arm64 docker compose file?
I want to avoid asking to edit files just for the app to work, I will try to figure out an elegant solution
Oh ok, thanks, yea editing files for the app to work isn't ideal as its just a temporary fix.
@Lancelot you can add a
docker-compose.arm64.json
btwI didn't knew, this is gonna be an easy fix
Epic
@techtimefor, it should be fixed now, sorry for the delay.
If Invidious is still installed in your runtipi, an update will appear for the app.
No worries, thanks for fixing it!
Seems like even after updating app stores I still get the same error, will try restarting runtipi.
If the error persist, can you send me the content of these files :
- runtipi/apps/migrated/invidious/docker-compose.yml
- runtipi/apps/migrated/invidious/docker-compose.arm64.yml
Sure
docker-compose.yml
docker-compose.arm64.yml
Can you also show me your logs when starting the app ?
I will try something dumb, sadly I don't have RPi anymore so I can't test it myself
ill be happy to test
Great, then you can add this as a new app-store :
https://github.com/runtipi/runtipi-appstore/tree/fix/invidious-arm
Then install install invidious from this appstore and check the logs.
sure
won't runtipi still install from main app store?
oh ok changed to the app store

Yes exactly
@Stavros, the
docker-compose.arm64.json
is ignored.
Did I missed something ? wrong name ? (the only difference inside is the image name)What the heck, I remember including the change maybe we removed it. Will look into it and make a pr if it's missing
managed to solve it by adding this to docker-compose.arm64.yml
after doing this it successfully installed

https://github.com/techtimefor/runtipi-appstore/blob/master/apps/invidious/docker-compose.arm64.yml
The issue mainly was tipi_main_network being undefined which was causing installation to fail but after defining the name of the external network it solved the issue (runtipi_tipi_main_network).
@Skullky thanks for all your help with getting Invidious working
tipi_main_network being undefined shows that it isn't being passed through properly or something else idk
It is strange that this issue only happens on Invidious of tipi_main_network being undefined but anyways at least Invidious works now.
Actually, we know where the issue come from. (sorry for the lack of explanation)
The docker-compose.arm64.yml should be automatically generated with the correct networks parameters.
Instead it relies on the already existing one which was not created to work with Runtipi v4.
It's probably our only app using separate docker images for arm64 and amd64.
We will fix this eventually, giving a seamless solution.
But, in the meantime, I have send a new update for Invidious :
When you go to the app config you will be asked your architecture.

@Nicolas we need this in a patch fix
This is not necessary anymore with the fix I pushed but I think you'll be interested by this guide whenever you will want to customize an app config : https://runtipi.io/docs/guides/customize-app-config
Customize app config
Homeserver management made easy
Thanks for the fix @Skullky
I'll fix this asap
Allowing an override section in the docker-compose.json
Tbh I liked the separate file idea
More complex update wise
But it's cleaner
You could do smth like "key:arm64" in the dynamic compose
GitHub
[REQUEST] Architecture specific override · Issue #2135 · runtipi/...
Is your feature request related to a problem? Please describe. When an app has different requirements for different architectures, I want a simple way to override or merge extra options in the dock...
I don't like seperate files
I'd rather have an approach similar to eslint for overrides
This
Oh I see
Thanks for fixing it, the guide is pretty handy too will look into it for sure.