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
techtimefor
techtimeforOP2w ago
Docker version 28.1.1, build 4eba377327
Stavros
Stavros2w ago
Please check here https://discord.com/channels/976934649643294750/1367422351163265106/1367422789019242506 It has instructions on how to solve the issue
techtimefor
techtimeforOP2w ago
[bob@piboi runtipi]$ sudo ./runtipi-cli start
[sudo] password for bob:
User permissions are ok
Copied system files
Generated .env file
File permissions ok
Images pulled
Existing containers stopped
Failed to start containers
Starting containers...
Starting containers... Debug: Container runtipi-db Creating
Container runtipi-queue Running
Container runtipi-db Created
Container runtipi Creating
Container runtipi Created
Container runtipi-reverse-proxy Creating
Container runtipi-reverse-proxy Created
Container runtipi-db Starting
Container runtipi-db Started
Container runtipi-db Waiting
Container runtipi-queue Waiting
Container runtipi-queue Error
Container runtipi-db Healthy
dependency failed to start: container runtipi-queue is unhealthy

[bob@piboi runtipi]$ sudo ./runtipi-cli stop
Tipi successfully stopped
[bob@piboi runtipi]$ sudo ./runtipi-cli start
User permissions are ok
Copied system files
Generated .env file
File permissions ok
Images pulled
Existing containers stopped
Containers started


╔════════════════════════ Runtipi started successfully ════════════════════════╗

Visit http://192.168.0.15:80 to access the dashboard ║

Find documentation and guides at: https://runtipi.io ║

Tipi is entirely written in TypeScript and we are looking for ║
contributors! ║

╚══════════════════════════════════════════════════════════════════════════════╝
[bob@piboi runtipi]$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b1690645b833 traefik:v3.2 "/entrypoint.sh --pr…" 56 seconds ago Up 16 seconds 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp runtipi-reverse-proxy
d066222b36bb ghcr.io/runtipi/runtipi:v4.0.0 "docker-entrypoint.s…" 56 seconds ago Up 37 seconds (healthy) 3000/tcp runtipi
c57d026438b6 rabbitmq:4-alpine "docker-entrypoint.s…" 57 seconds ago Up 54 seconds (healthy) 4369/tcp, 5671-5672/tcp, 15691-15692/tcp, 25672/tcp runtipi-queue
88642b14abf2 postgres:14 "docker-entrypoint.s…" 57 seconds ago Up 54 seconds (healthy) 5432/tcp runtipi-db
[bob@piboi runtipi]$
[bob@piboi runtipi]$ sudo ./runtipi-cli start
[sudo] password for bob:
User permissions are ok
Copied system files
Generated .env file
File permissions ok
Images pulled
Existing containers stopped
Failed to start containers
Starting containers...
Starting containers... Debug: Container runtipi-db Creating
Container runtipi-queue Running
Container runtipi-db Created
Container runtipi Creating
Container runtipi Created
Container runtipi-reverse-proxy Creating
Container runtipi-reverse-proxy Created
Container runtipi-db Starting
Container runtipi-db Started
Container runtipi-db Waiting
Container runtipi-queue Waiting
Container runtipi-queue Error
Container runtipi-db Healthy
dependency failed to start: container runtipi-queue is unhealthy

[bob@piboi runtipi]$ sudo ./runtipi-cli stop
Tipi successfully stopped
[bob@piboi runtipi]$ sudo ./runtipi-cli start
User permissions are ok
Copied system files
Generated .env file
File permissions ok
Images pulled
Existing containers stopped
Containers started


╔════════════════════════ Runtipi started successfully ════════════════════════╗

Visit http://192.168.0.15:80 to access the dashboard ║

Find documentation and guides at: https://runtipi.io ║

Tipi is entirely written in TypeScript and we are looking for ║
contributors! ║

╚══════════════════════════════════════════════════════════════════════════════╝
[bob@piboi runtipi]$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b1690645b833 traefik:v3.2 "/entrypoint.sh --pr…" 56 seconds ago Up 16 seconds 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp runtipi-reverse-proxy
d066222b36bb ghcr.io/runtipi/runtipi:v4.0.0 "docker-entrypoint.s…" 56 seconds ago Up 37 seconds (healthy) 3000/tcp runtipi
c57d026438b6 rabbitmq:4-alpine "docker-entrypoint.s…" 57 seconds ago Up 54 seconds (healthy) 4369/tcp, 5671-5672/tcp, 15691-15692/tcp, 25672/tcp runtipi-queue
88642b14abf2 postgres:14 "docker-entrypoint.s…" 57 seconds ago Up 54 seconds (healthy) 5432/tcp runtipi-db
[bob@piboi runtipi]$
works fine now
Stavros
Stavros2w ago
It's a small bug and we will fix it in the next update
techtimefor
techtimeforOP2w ago
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.
runtipi | info > Installing app invidious:migrated as User ID: 0, Group ID: 0
runtipi | info > Deleting app invidious:migrated folder if exists
runtipi | info > Creating app invidious:migrated folder
runtipi | info > Creating app invidious:migrated data folder
runtipi | info > Copying app invidious:migrated from repo migrated
runtipi | info > Creating app.env file for app invidious:migrated
runtipi | info > Copying data dir for app invidious:migrated
runtipi | info > Running docker compose with args --env-file /app-data/migrated/invidious/app.env --project-name invidious_migrated -f /data/apps/migrated/invidious/docker-compose.arm64.yml down --rmi all --remove-orphans
runtipi | info > docker-compose: time="2025-05-01T15:11:03Z" level=warning msg="/data/apps/migrated/invidious/docker-compose.arm64.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
runtipi | info > docker-compose: service "inv_sig_helper" refers to undefined network tipi_main_network: invalid compose project
runtipi | info > Docker-compose exited with code 1
runtipi | warn > No prior containers to remove for app invidious:migrated
runtipi | info > Running docker compose with args --env-file /app-data/migrated/invidious/app.env --project-name invidious_migrated -f /data/apps/migrated/invidious/docker-compose.arm64.yml up --detach --force-recreate --remove-orphans --pull always
runtipi | info > docker-compose: time="2025-05-01T15:11:03Z" level=warning msg="/data/apps/migrated/invidious/docker-compose.arm64.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
runtipi | info > docker-compose: service "inv_sig_helper" refers to undefined network tipi_main_network: invalid compose project
runtipi | info > Docker-compose exited with code 1
runtipi | error > Failed to install app invidious:migrated: service "inv_sig_helper" refers to undefined network tipi_main_network: invalid compose project
runtipi | info > Installing app invidious:migrated as User ID: 0, Group ID: 0
runtipi | info > Deleting app invidious:migrated folder if exists
runtipi | info > Creating app invidious:migrated folder
runtipi | info > Creating app invidious:migrated data folder
runtipi | info > Copying app invidious:migrated from repo migrated
runtipi | info > Creating app.env file for app invidious:migrated
runtipi | info > Copying data dir for app invidious:migrated
runtipi | info > Running docker compose with args --env-file /app-data/migrated/invidious/app.env --project-name invidious_migrated -f /data/apps/migrated/invidious/docker-compose.arm64.yml down --rmi all --remove-orphans
runtipi | info > docker-compose: time="2025-05-01T15:11:03Z" level=warning msg="/data/apps/migrated/invidious/docker-compose.arm64.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
runtipi | info > docker-compose: service "inv_sig_helper" refers to undefined network tipi_main_network: invalid compose project
runtipi | info > Docker-compose exited with code 1
runtipi | warn > No prior containers to remove for app invidious:migrated
runtipi | info > Running docker compose with args --env-file /app-data/migrated/invidious/app.env --project-name invidious_migrated -f /data/apps/migrated/invidious/docker-compose.arm64.yml up --detach --force-recreate --remove-orphans --pull always
runtipi | info > docker-compose: time="2025-05-01T15:11:03Z" level=warning msg="/data/apps/migrated/invidious/docker-compose.arm64.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
runtipi | info > docker-compose: service "inv_sig_helper" refers to undefined network tipi_main_network: invalid compose project
runtipi | info > Docker-compose exited with code 1
runtipi | error > Failed to install app invidious:migrated: service "inv_sig_helper" refers to undefined network tipi_main_network: invalid compose project
Stavros
Stavros2w ago
Are all of your apps up to date?
techtimefor
techtimeforOP2w ago
yep only invidious fails to install
Stavros
Stavros2w ago
@Lancelot what do you think? summoned the appstore guy
Skullky
Skullky2w ago
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.
techtimefor
techtimeforOP2w ago
Will it require modifying the arm64 docker compose file?
Skullky
Skullky2w ago
I want to avoid asking to edit files just for the app to work, I will try to figure out an elegant solution
techtimefor
techtimeforOP2w ago
Oh ok, thanks, yea editing files for the app to work isn't ideal as its just a temporary fix.
Stavros
Stavros2w ago
@Lancelot you can add a docker-compose.arm64.json btw
Skullky
Skullky2w ago
I didn't knew, this is gonna be an easy fix
techtimefor
techtimeforOP2w ago
Epic
Skullky
Skullky2w ago
@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.
techtimefor
techtimeforOP7d ago
No worries, thanks for fixing it! Seems like even after updating app stores I still get the same error, will try restarting runtipi.
Skullky
Skullky7d ago
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
techtimefor
techtimeforOP7d ago
Sure docker-compose.yml
services:
invidious:
image: quay.io/invidious/invidious:master
restart: unless-stopped
networks:
invidious_migrated_network:
gw_priority: 0
tipi_main_network:
gw_priority: 1
healthcheck:
test: wget -nv --tries=1 --spider http://127.0.0.1:3000/api/v1/trending || exit
1
interval: 30s
timeout: 5s
retries: 2
environment:
INVIDIOUS_CONFIG: |
db:
dbname: invidious
user: tipi
password: tipi
host: invidious-db
port: 5432
check_tables: true
hmac_key: ${INVIDIOUS_HMAC_KEY}
use_innertube_for_captions: true
domain: ${INVIDIOUS_DOMAIN}
external_port: ${INVIDIOUS_EXTERNAL_PORT:-${APP_PORT}}
https_only: ${INVIDIOUS_HTTPS_ONLY}
signature_server: inv_sig_helper:12999
visitor_data: ${INVIDIOUS_VISITOR_DATA}
po_token: ${INVIDIOUS_PO_TOKEN}
ports:
- ${APP_PORT}:3000
depends_on:
invidious-db:
condition: service_healthy
inv_sig_helper:
condition: service_started
labels:
runtipi.managed: true
inv_sig_helper:
image: quay.io/invidious/inv-sig-helper:latest
command:
- --tcp
- 0.0.0.0:12999
restart: unless-stopped
networks:
invidious_migrated_network:
gw_priority: 0
environment:
RUST_LOG: info
labels:
runtipi.managed: true
cap_drop:
- ALL
read_only: true
security_opt:
- no-new-privileges:true
invidious-db:
image: postgres:14
restart: unless-stopped
networks:
invidious_migrated_network:
gw_priority: 0
healthcheck:
test: pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB
environment:
POSTGRES_DB: invidious
POSTGRES_USER: tipi
POSTGRES_PASSWORD: tipi
volumes:
- ${APP_DATA_DIR}/data/postgres:/var/lib/postgresql/data
- ${APP_DATA_DIR}/data/init/sql:/config/sql
- ${APP_DATA_DIR}/data/init/init-invidious-db.sh:/docker-entrypoint-initdb.d/init-invidious-db.sh
labels:
runtipi.managed: true
networks:
tipi_main_network:
name: runtipi_tipi_main_network
external: true
invidious_migrated_network:
external: false
ipam:
config:
- subnet: 10.128.16.0/24
services:
invidious:
image: quay.io/invidious/invidious:master
restart: unless-stopped
networks:
invidious_migrated_network:
gw_priority: 0
tipi_main_network:
gw_priority: 1
healthcheck:
test: wget -nv --tries=1 --spider http://127.0.0.1:3000/api/v1/trending || exit
1
interval: 30s
timeout: 5s
retries: 2
environment:
INVIDIOUS_CONFIG: |
db:
dbname: invidious
user: tipi
password: tipi
host: invidious-db
port: 5432
check_tables: true
hmac_key: ${INVIDIOUS_HMAC_KEY}
use_innertube_for_captions: true
domain: ${INVIDIOUS_DOMAIN}
external_port: ${INVIDIOUS_EXTERNAL_PORT:-${APP_PORT}}
https_only: ${INVIDIOUS_HTTPS_ONLY}
signature_server: inv_sig_helper:12999
visitor_data: ${INVIDIOUS_VISITOR_DATA}
po_token: ${INVIDIOUS_PO_TOKEN}
ports:
- ${APP_PORT}:3000
depends_on:
invidious-db:
condition: service_healthy
inv_sig_helper:
condition: service_started
labels:
runtipi.managed: true
inv_sig_helper:
image: quay.io/invidious/inv-sig-helper:latest
command:
- --tcp
- 0.0.0.0:12999
restart: unless-stopped
networks:
invidious_migrated_network:
gw_priority: 0
environment:
RUST_LOG: info
labels:
runtipi.managed: true
cap_drop:
- ALL
read_only: true
security_opt:
- no-new-privileges:true
invidious-db:
image: postgres:14
restart: unless-stopped
networks:
invidious_migrated_network:
gw_priority: 0
healthcheck:
test: pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB
environment:
POSTGRES_DB: invidious
POSTGRES_USER: tipi
POSTGRES_PASSWORD: tipi
volumes:
- ${APP_DATA_DIR}/data/postgres:/var/lib/postgresql/data
- ${APP_DATA_DIR}/data/init/sql:/config/sql
- ${APP_DATA_DIR}/data/init/init-invidious-db.sh:/docker-entrypoint-initdb.d/init-invidious-db.sh
labels:
runtipi.managed: true
networks:
tipi_main_network:
name: runtipi_tipi_main_network
external: true
invidious_migrated_network:
external: false
ipam:
config:
- subnet: 10.128.16.0/24
docker-compose.arm64.yml
version: "3.7"
services:
invidious:
container_name: invidious
image: quay.io/invidious/invidious:master-arm64
restart: unless-stopped
depends_on:
invidious-db:
condition: service_healthy
inv_sig_helper:
condition: service_started
ports:
- "${APP_PORT}:3000"
environment:
INVIDIOUS_CONFIG: |
db:
dbname: invidious
user: tipi
password: tipi
host: invidious-db
port: 5432
check_tables: true
hmac_key: ${INVIDIOUS_HMAC_KEY}
use_innertube_for_captions: true
domain: ${INVIDIOUS_DOMAIN}
external_port: ${INVIDIOUS_EXTERNAL_PORT:-${APP_PORT}}
https_only: ${INVIDIOUS_HTTPS_ONLY}
signature_server: inv_sig_helper:12999
visitor_data: ${INVIDIOUS_VISITOR_DATA}
po_token: ${INVIDIOUS_PO_TOKEN}
healthcheck:
test: wget -nv --tries=1 --spider http://127.0.0.1:3000/api/v1/trending || exit 1
interval: 30s
timeout: 5s
retries: 2
networks:
- tipi_main_network
labels:
# Main
traefik.enable: true
traefik.http.middlewares.invidious-web-redirect.redirectscheme.scheme: https
traefik.http.services.invidious.loadbalancer.server.port: 3000
# Web
traefik.http.routers.invidious-insecure.rule: Host(`${APP_DOMAIN}`)
traefik.http.routers.invidious-insecure.entrypoints: web
traefik.http.routers.invidious-insecure.service: invidious
traefik.http.routers.invidious-insecure.middlewares: invidious-web-redirect
# Websecure
traefik.http.routers.invidious.rule: Host(`${APP_DOMAIN}`)
traefik.http.routers.invidious.entrypoints: websecure
traefik.http.routers.invidious.service: invidious
traefik.http.routers.invidious.tls.certresolver: myresolver
# Local domain
traefik.http.routers.invidious-local-insecure.rule: Host(`invidious.${LOCAL_DOMAIN}`)
traefik.http.routers.invidious-local-insecure.entrypoints: web
traefik.http.routers.invidious-local-insecure.service: invidious
traefik.http.routers.invidious-local-insecure.middlewares: invidious-web-redirect
# Local domain secure
traefik.http.routers.invidious-local.rule: Host(`invidious.${LOCAL_DOMAIN}`)
traefik.http.routers.invidious-local.entrypoints: websecure
traefik.http.routers.invidious-local.service: invidious
traefik.http.routers.invidious-local.tls: true
runtipi.managed: true

inv_sig_helper:
container_name: inv_sig_helper
image: quay.io/invidious/inv-sig-helper:latest
command: ["--tcp", "0.0.0.0:12999"]
environment:
- RUST_LOG=info
restart: unless-stopped
cap_drop:
- ALL
read_only: true
security_opt:
- no-new-privileges:true
networks:
- tipi_main_network
labels:
runtipi.managed: true

invidious-db:
container_name: invidious-db
image: postgres:14
restart: unless-stopped
volumes:
- ${APP_DATA_DIR}/data/postgres:/var/lib/postgresql/data
- ${APP_DATA_DIR}/data/init/sql:/config/sql
- ${APP_DATA_DIR}/data/init/init-invidious-db.sh:/docker-entrypoint-initdb.d/init-invidious-db.sh
environment:
POSTGRES_DB: invidious
POSTGRES_USER: tipi
POSTGRES_PASSWORD: tipi
healthcheck:
test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB"]
networks:
- tipi_main_network
version: "3.7"
services:
invidious:
container_name: invidious
image: quay.io/invidious/invidious:master-arm64
restart: unless-stopped
depends_on:
invidious-db:
condition: service_healthy
inv_sig_helper:
condition: service_started
ports:
- "${APP_PORT}:3000"
environment:
INVIDIOUS_CONFIG: |
db:
dbname: invidious
user: tipi
password: tipi
host: invidious-db
port: 5432
check_tables: true
hmac_key: ${INVIDIOUS_HMAC_KEY}
use_innertube_for_captions: true
domain: ${INVIDIOUS_DOMAIN}
external_port: ${INVIDIOUS_EXTERNAL_PORT:-${APP_PORT}}
https_only: ${INVIDIOUS_HTTPS_ONLY}
signature_server: inv_sig_helper:12999
visitor_data: ${INVIDIOUS_VISITOR_DATA}
po_token: ${INVIDIOUS_PO_TOKEN}
healthcheck:
test: wget -nv --tries=1 --spider http://127.0.0.1:3000/api/v1/trending || exit 1
interval: 30s
timeout: 5s
retries: 2
networks:
- tipi_main_network
labels:
# Main
traefik.enable: true
traefik.http.middlewares.invidious-web-redirect.redirectscheme.scheme: https
traefik.http.services.invidious.loadbalancer.server.port: 3000
# Web
traefik.http.routers.invidious-insecure.rule: Host(`${APP_DOMAIN}`)
traefik.http.routers.invidious-insecure.entrypoints: web
traefik.http.routers.invidious-insecure.service: invidious
traefik.http.routers.invidious-insecure.middlewares: invidious-web-redirect
# Websecure
traefik.http.routers.invidious.rule: Host(`${APP_DOMAIN}`)
traefik.http.routers.invidious.entrypoints: websecure
traefik.http.routers.invidious.service: invidious
traefik.http.routers.invidious.tls.certresolver: myresolver
# Local domain
traefik.http.routers.invidious-local-insecure.rule: Host(`invidious.${LOCAL_DOMAIN}`)
traefik.http.routers.invidious-local-insecure.entrypoints: web
traefik.http.routers.invidious-local-insecure.service: invidious
traefik.http.routers.invidious-local-insecure.middlewares: invidious-web-redirect
# Local domain secure
traefik.http.routers.invidious-local.rule: Host(`invidious.${LOCAL_DOMAIN}`)
traefik.http.routers.invidious-local.entrypoints: websecure
traefik.http.routers.invidious-local.service: invidious
traefik.http.routers.invidious-local.tls: true
runtipi.managed: true

inv_sig_helper:
container_name: inv_sig_helper
image: quay.io/invidious/inv-sig-helper:latest
command: ["--tcp", "0.0.0.0:12999"]
environment:
- RUST_LOG=info
restart: unless-stopped
cap_drop:
- ALL
read_only: true
security_opt:
- no-new-privileges:true
networks:
- tipi_main_network
labels:
runtipi.managed: true

invidious-db:
container_name: invidious-db
image: postgres:14
restart: unless-stopped
volumes:
- ${APP_DATA_DIR}/data/postgres:/var/lib/postgresql/data
- ${APP_DATA_DIR}/data/init/sql:/config/sql
- ${APP_DATA_DIR}/data/init/init-invidious-db.sh:/docker-entrypoint-initdb.d/init-invidious-db.sh
environment:
POSTGRES_DB: invidious
POSTGRES_USER: tipi
POSTGRES_PASSWORD: tipi
healthcheck:
test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB"]
networks:
- tipi_main_network
Skullky
Skullky7d ago
Can you also show me your logs when starting the app ?
techtimefor
techtimeforOP7d ago
runtipi | info > Installing app invidious:migrated as User ID: 0, Group ID: 0
runtipi | info > Deleting app invidious:migrated folder if exists
runtipi | info > App vaultwarden:migrated started successfully
runtipi | info > Creating app invidious:migrated folder
runtipi | info > Creating app invidious:migrated data folder
runtipi | info > Copying app invidious:migrated from repo migrated
runtipi | info > Creating app.env file for app invidious:migrated
runtipi | info > Copying data dir for app invidious:migrated
runtipi | info > Allocated subnet 10.128.16.0/24 for app invidious:migrated
runtipi | info > Running docker compose with args --env-file /app-data/migrated/invidious/app.env --project-name invidious_migrated -f /data/apps/migrated/invidious/docker-compose.arm64.yml down --rmi all --remove-orphans
runtipi | info > docker-compose: time="2025-05-04T13:04:26Z" level=warning msg="/data/apps/migrated/invidious/docker-compose.arm64.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
runtipi | info > docker-compose: service "invidious" refers to undefined network tipi_main_network: invalid compose project
runtipi | info > Docker-compose exited with code 1
runtipi | warn > No prior containers to remove for app invidious:migrated
runtipi | info > Running docker compose with args --env-file /app-data/migrated/invidious/app.env --project-name invidious_migrated -f /data/apps/migrated/invidious/docker-compose.arm64.yml up --detach --force-recreate --remove-orphans --pull always
runtipi | info > docker-compose: time="2025-05-04T13:04:27Z" level=warning msg="/data/apps/migrated/invidious/docker-compose.arm64.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
runtipi | info > docker-compose: service "invidious" refers to undefined network tipi_main_network: invalid compose project
runtipi | info > Docker-compose exited with code 1
runtipi | error > Failed to install app invidious:migrated: service "invidious" refers to undefined network tipi_main_network: invalid compose project
runtipi | info > Installing app invidious:migrated as User ID: 0, Group ID: 0
runtipi | info > Deleting app invidious:migrated folder if exists
runtipi | info > App vaultwarden:migrated started successfully
runtipi | info > Creating app invidious:migrated folder
runtipi | info > Creating app invidious:migrated data folder
runtipi | info > Copying app invidious:migrated from repo migrated
runtipi | info > Creating app.env file for app invidious:migrated
runtipi | info > Copying data dir for app invidious:migrated
runtipi | info > Allocated subnet 10.128.16.0/24 for app invidious:migrated
runtipi | info > Running docker compose with args --env-file /app-data/migrated/invidious/app.env --project-name invidious_migrated -f /data/apps/migrated/invidious/docker-compose.arm64.yml down --rmi all --remove-orphans
runtipi | info > docker-compose: time="2025-05-04T13:04:26Z" level=warning msg="/data/apps/migrated/invidious/docker-compose.arm64.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
runtipi | info > docker-compose: service "invidious" refers to undefined network tipi_main_network: invalid compose project
runtipi | info > Docker-compose exited with code 1
runtipi | warn > No prior containers to remove for app invidious:migrated
runtipi | info > Running docker compose with args --env-file /app-data/migrated/invidious/app.env --project-name invidious_migrated -f /data/apps/migrated/invidious/docker-compose.arm64.yml up --detach --force-recreate --remove-orphans --pull always
runtipi | info > docker-compose: time="2025-05-04T13:04:27Z" level=warning msg="/data/apps/migrated/invidious/docker-compose.arm64.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
runtipi | info > docker-compose: service "invidious" refers to undefined network tipi_main_network: invalid compose project
runtipi | info > Docker-compose exited with code 1
runtipi | error > Failed to install app invidious:migrated: service "invidious" refers to undefined network tipi_main_network: invalid compose project
Skullky
Skullky7d ago
I will try something dumb, sadly I don't have RPi anymore so I can't test it myself
techtimefor
techtimeforOP7d ago
ill be happy to test
Skullky
Skullky7d ago
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.
techtimefor
techtimeforOP7d ago
sure won't runtipi still install from main app store?
techtimefor
techtimeforOP7d ago
oh ok changed to the app store
No description
Skullky
Skullky7d ago
Yes exactly
techtimefor
techtimeforOP7d ago
runtipi | info > Installing app invidious:testing as User ID: 0, Group ID: 0
runtipi | info > Deleting app invidious:testing folder if exists
runtipi | info > Creating app invidious:testing folder
runtipi | info > Creating app invidious:testing data folder
runtipi | info > Copying app invidious:testing from repo testing
runtipi | info > Creating app.env file for app invidious:testing
runtipi | info > Copying data dir for app invidious:testing
runtipi | info > Allocated subnet 10.128.16.0/24 for app invidious:testing
runtipi | info > Running docker compose with args --env-file /app-data/testing/invidious/app.env --project-name invidious_testing -f /data/apps/testing/invidious/docker-compose.yml down --rmi all --remove-orphans
runtipi | info > docker-compose: Image postgres:14 Removing
runtipi | info > docker-compose: Image postgres:14 Resource is still in use
runtipi | info > Running docker compose with args --env-file /app-data/testing/invidious/app.env --project-name invidious_testing -f /data/apps/testing/invidious/docker-compose.yml up --detach --force-recreate --remove-orphans --pull always
runtipi | info > docker-compose: invidious Pulling
runtipi | inv_sig_helper Pulling
runtipi | invidious-db Pulling
runtipi | info > docker-compose: invidious-db Pulled
runtipi | info > docker-compose: 168a9c4e4eec Pulling fs layer
runtipi | f74914ed26bb Pulling fs layer
runtipi | 133eeb9eb7d4 Pulling fs layer
runtipi | 4f4fb700ef54 Pulling fs layer
runtipi | 4f4fb700ef54 Waiting
runtipi | info > docker-compose: no matching manifest for linux/arm64/v8 in the manifest list entries
runtipi | info > Docker-compose exited with code 1
runtipi | error > Failed to install app invidious:testing: no matching manifest for linux/arm64/v8 in the manifest list entries
runtipi | info > Installing app invidious:testing as User ID: 0, Group ID: 0
runtipi | info > Deleting app invidious:testing folder if exists
runtipi | info > Creating app invidious:testing folder
runtipi | info > Creating app invidious:testing data folder
runtipi | info > Copying app invidious:testing from repo testing
runtipi | info > Creating app.env file for app invidious:testing
runtipi | info > Copying data dir for app invidious:testing
runtipi | info > Allocated subnet 10.128.16.0/24 for app invidious:testing
runtipi | info > Running docker compose with args --env-file /app-data/testing/invidious/app.env --project-name invidious_testing -f /data/apps/testing/invidious/docker-compose.yml down --rmi all --remove-orphans
runtipi | info > docker-compose: Image postgres:14 Removing
runtipi | info > docker-compose: Image postgres:14 Resource is still in use
runtipi | info > Running docker compose with args --env-file /app-data/testing/invidious/app.env --project-name invidious_testing -f /data/apps/testing/invidious/docker-compose.yml up --detach --force-recreate --remove-orphans --pull always
runtipi | info > docker-compose: invidious Pulling
runtipi | inv_sig_helper Pulling
runtipi | invidious-db Pulling
runtipi | info > docker-compose: invidious-db Pulled
runtipi | info > docker-compose: 168a9c4e4eec Pulling fs layer
runtipi | f74914ed26bb Pulling fs layer
runtipi | 133eeb9eb7d4 Pulling fs layer
runtipi | 4f4fb700ef54 Pulling fs layer
runtipi | 4f4fb700ef54 Waiting
runtipi | info > docker-compose: no matching manifest for linux/arm64/v8 in the manifest list entries
runtipi | info > Docker-compose exited with code 1
runtipi | error > Failed to install app invidious:testing: no matching manifest for linux/arm64/v8 in the manifest list entries
Skullky
Skullky7d ago
@Stavros, the docker-compose.arm64.json is ignored. Did I missed something ? wrong name ? (the only difference inside is the image name)
Stavros
Stavros7d ago
What the heck, I remember including the change maybe we removed it. Will look into it and make a pr if it's missing
techtimefor
techtimeforOP7d ago
managed to solve it by adding this to docker-compose.arm64.yml
networks:
tipi_main_network:
external:
name: runtipi_tipi_main_network
networks:
tipi_main_network:
external:
name: runtipi_tipi_main_network
after doing this it successfully installed
techtimefor
techtimeforOP7d ago
No description
techtimefor
techtimeforOP6d ago
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.
Skullky
Skullky6d ago
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.
Skullky
Skullky6d ago
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.
No description
Stavros
Stavros6d ago
@Nicolas we need this in a patch fix
Skullky
Skullky6d ago
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
Nicolas
Nicolas6d ago
Thanks for the fix @Skullky I'll fix this asap Allowing an override section in the docker-compose.json
Stavros
Stavros6d ago
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
Nicolas
Nicolas6d ago
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...
Nicolas
Nicolas6d ago
I don't like seperate files I'd rather have an approach similar to eslint for overrides
Stavros
Stavros6d ago
This
techtimefor
techtimeforOP6d ago
Oh I see Thanks for fixing it, the guide is pretty handy too will look into it for sure.

Did you find this page helpful?