live-dl icon indicating copy to clipboard operation
live-dl copied to clipboard

Failed to start container on latest version

Open A1exMinatoooo opened this issue 3 years ago • 2 comments

docker-compose.yml:

version: '3'

x-defaults: &defaults
  image: sparanoid/live-dl:latest
  restart: always
  volumes:
    - /volume2/NAS/live-dl/config.yml:/app/config.yml
    - /volume2/NAS/live-dl/youtube.com_cookies.txt:/app/cookies.txt
    - /volume2/NAS/Downloads/live-dl:/app/downloads

services:
  minatoaqua:
    <<: *defaults
    command: https://www.youtube.com/channel/UC1opHUrw8rvnsadT-iGp7Cg --debug

docker-compose logs

root@Alex-NAS:/volume2/NAS/live-dl# docker-compose logs
Attaching to live-dl_minatoaqua_1
minatoaqua_1  | standard_init_linux.go:230: exec user process caused: no such file or directory
minatoaqua_1  | standard_init_linux.go:230: exec user process caused: no such file or directory
minatoaqua_1  | standard_init_linux.go:230: exec user process caused: no such file or directory

It just kept restarting and didn't print any other error logs.

btw, how can I add a twicasting recording task by editing the docker-compose file?

A1exMinatoooo avatar Jan 10 '22 08:01 A1exMinatoooo

The example you provided works for me. Try to update your latest tag by docker compose pull or use the edge version sparanoid/live-dl:edge.

And this project only works for YouTube streams and videos.

sparanoid avatar Jan 10 '22 18:01 sparanoid

The example you provided works for me. Try to update your latest tag by docker compose pull or use the edge version sparanoid/live-dl:edge.

And this project only works for YouTube streams and videos.

kinda weird, I tried directly run by using following command:

docker run -itd \
  --name live-dl_minatoaqua \
  -v /volume2/NAS/Downloads/live-dl:/app/downloads \
  -v /volume2/NAS/live-dl/config.yml:/app/config.yml \
  -v /volume2/NAS/live-dl/youtube.com_cookies.txt:/app/cookies.txt \
  sparanoid/live-dl:edge \
  'UC1opHUrw8rvnsadT-iGp7Cg'

returned the same error.

maybe some mysterious error caused by synology? or did I miss some other configuration?

A1exMinatoooo avatar Jan 11 '22 02:01 A1exMinatoooo