YoutubeDL-Material: [BUG] v.4.3 docker fails to start with exit code 243
Describe the bug Docker-compose file that ran previous nightly (nightly-2022-06-22) fine, stops immediately on 4.3 with code 243
version: "3.5"
services:
ytdl_material:
# image: tzahi12345/youtubedl-material:nightly-2022-06-22
image: tzahi12345/youtubedl-material:4.3
container_name: ytdl_material
environment:
ALLOW_CONFIG_MUTATIONS: 'true'
write_ytdl_config: 'true'
ytdl_mongodb_connection_string: 'mongodb://ytdl-mongo-db:27017'
ytdl_use_local_db: 'false'
ytdl_port: 9998
UID: 1026
GID: 100
volumes:
- /volume1/docker/youtube-dlm/appdata:/app/appdata
- /volume1/video/YoutubeAudio:/app/audio
- /volume1/video/YoutubeDLM/Singles:/app/video
- /volume1/video/YoutubeDLM:/app/subscriptions
ports:
- 9998:9998/tcp
networks:
- ytdl
depends_on:
- ytdl-mongo-db
restart: "no"
ytdl-mongo-db:
image: mongo:4
container_name: mongo-db
ports:
- 27017:27017
networks:
- ytdl
logging:
driver: "none"
volumes:
- /volume1/docker/youtube-dlm/db/:/data/db
restart: always
networks:
ytdl:
name: ytdl
Environment
- Version 4.3
- Docker tag: latest/4.3
- Docker tag nightly-2022-06-22 works
From https://github.com/Tzahi12345/YoutubeDL-Material/pull/117 I assume that error code is related to node/npm.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 41 (10 by maintainers)
Glad I found this, I would like to mention that I have the exact same issue since I pulled 4.3 a few minutes ago. The container doesn’t start with uid/gid like it did with the Nightlies. Unfortunately I need to have uid/gid because access permissions are set this way. Interestingly I have the same setup as @AlexFullmoon Docker running on Synology with BTRFS Volume.
Alright should be fixed now (works on my end). Image will be updated in an hour or so if someone can test it out! Commit: fc3c179f6a7ae75554d51a15504f14cc389f3dd3
Yep, sorry for that, i checked twice yet some rouge
>
existSo looking by entrypoint.sh here , it should be taking effect but don’t? 🤔
Docker logs are empty, container stops before any logs are written.
appdata/logs
also remains empty. Any other way to get any logs?Tried with empty
appdata
, same story.I didn’t say it’s the same issue, just that it gives same error code so might be a bit related.