[BUG] container won't start about youtubedl-material HOT 8 OPEN

I have the same issue with the latest docker-compose at start. 😢

[entrypoint] setup permission, this may take a while
[email protected] start
pm2-runtime --raw pm2.config.js
npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /.npm
npm ERR! errno -13

npm ERR! Your cache folder contains root-owned files, due to a bug in
npm ERR! previous versions of npm which has since been addressed.

from youtubedl-material.

I also just installed it on DS918+ with DSM 7.1.1. With latest tag it does not work when using different UID/GID, but nightly was fine.

I only created the necessary folders in advance. Did you try without UID/GID?

Content of my docker-compose.yml:

version: "2"
services:
    ytdl_material:
        environment: 
            UID: 1025
            GID: 100
            ytdl_mongodb_connection_string: 'mongodb://ytdl-mongo-db:27017'
            ytdl_use_local_db: 'false'
            write_ytdl_config: 'true'
        restart: always
        depends_on:
            - ytdl-mongo-db
        volumes:
            - ./appdata:/app/appdata
            - ./audio:/app/audio
            - /volume1/Public/MusicVideos:/app/video
            - ./subscriptions:/app/subscriptions
            - ./users:/app/users
        ports:
            - "8998:17442"
        #image: tzahi12345/youtubedl-material:latest
        image: tzahi12345/youtubedl-material:nightly
    ytdl-mongo-db:
        image: mongo:4
        logging:
            driver: "none"          
        container_name: mongo-db
        restart: always
        volumes:
            - ./db/:/data/db

from youtubedl-material.

after restart container i see this

from youtubedl-material.

Error: listen EACCES: permission denied 0.0.0.0:443

Sounds like the container has a problem with the network setup. What settings are you using, @Monoboy4ik ? Are you running in privileged mode, maybe?

from youtubedl-material.

Error: listen EACCES: permission denied 0.0.0.0:443

Sounds like the container has a problem with the network setup. What settings are you using, @Monoboy4ik ? Are you running in privileged mode, maybe?

I found out that if I change the port in the settings from 17442 to 443 (I use a reverse proxy), then the container does not start

services:
ytdl_material:
environment:
- ytdl_mongodb_connection_string=mongodb://ytdl-mongo-db:27017
- ytdl_use_local_db=false
- write_ytdl_config=true
- PUID=1026
- PGID=100
restart: always
depends_on:
- ytdl-mongo-db
volumes:
- /volume2/docker/ytdl/appdata:/app/appdata
- /volume2/docker/ytdl/audio:/app/audio
- /volume2/docker/ytdl/video:/app/video
- /volume2/docker/ytdl/subscriptions:/app/subscriptions
- /volume2/docker/ytdl/users:/app/users
- /volume2/downloads:/app/downloads
ports:
- 8998:17442
image: tzahi12345/youtubedl-material:nightly
ytdl-mongo-db:
# If you are using a Raspberry Pi, use mongo:4.4.18
image: mongo:4
logging:
driver: "none"
container_name: mongo-db
restart: always
volumes:
- /volume2/docker/ytdl/db/:/data/db

from youtubedl-material.

I see. But the reverse proxy should allow to map any port to the "outside" world, right?
I guess port 443 is restricted and requires additional access rights inside the container. So only when the user would be root, it can work.

from youtubedl-material.

you're right, I added "privileged: true" but it didn't help

from youtubedl-material.

I thought that these settings only affect the formation of the correct link to the downloaded file, but it looks like another proxy is trying to rise inside the container...

from youtubedl-material.