techtimefor
techtimefor
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
Thanks for fixing it, the guide is pretty handy too will look into it for sure.
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
Oh I see
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
It is strange that this issue only happens on Invidious of tipi_main_network being undefined but anyways at least Invidious works now.
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
tipi_main_network being undefined shows that it isn't being passed through properly or something else idk
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
@Skullky thanks for all your help with getting Invidious working
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
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).
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
No description
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
after doing this it successfully installed
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
networks:
tipi_main_network:
external:
name: runtipi_tipi_main_network
networks:
tipi_main_network:
external:
name: runtipi_tipi_main_network
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
managed to solve it by adding this to docker-compose.arm64.yml
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
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
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
No description
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
won't runtipi still install from main app store?
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
sure
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
ill be happy to test
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
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
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
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
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
docker-compose.arm64.yml
71 replies
RRuntipi
Created by techtimefor on 5/1/2025 in #🙋🏼・help
Issues when starting runtipi-queue container
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
71 replies