You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before opening an issue make sure that there are no duplicates and that you are on the latest version. Describe the bug
I run the setup. Add the YT app code, exit and then the docker container... but the config isn't found.
Using Debian12 via SSH.
To Reproduce
Steps to reproduce the behavior:
Run the following setup: docker run --rm -it -v data:/app/data --net=host -e TERM=$TERM -e COLORTERM=$COLORTERM ghcr.io/dmunozv04/isponsorblocktv --setup
Select the skips and enter the Roku code from the TV app. Save. Exit.
docker compose up [+] Running 2/2
✔ Network sponsorblock_default Created 0.1s
✔ Container iSponsorBlockTV Created 0.1s
Attaching to iSponsorBlockTV
iSponsorBlockTV | Could not load config file
iSponsorBlockTV | Blank config file created
iSponsorBlockTV | No devices found, please add at least one device
iSponsorBlockTV | Exiting in 10 seconds...
[+] Stopping 1/1
✔ Container iSponsorBlockTV Stopped
Expected behavior
No Could not load config file
iSponsorBlockTV server (please complete the following information):
OS: Docker on Debian12
Appreciate any help here. Seems so simple, yet...
The text was updated successfully, but these errors were encountered:
Before opening an issue make sure that there are no duplicates and that you are on the latest version.
Describe the bug
I run the setup. Add the YT app code, exit and then the docker container... but the config isn't found.
Using Debian12 via SSH.
To Reproduce
Steps to reproduce the behavior:
docker run --rm -it -v data:/app/data --net=host -e TERM=$TERM -e COLORTERM=$COLORTERM ghcr.io/dmunozv04/isponsorblocktv --setup
docker compose up
Then this:
Expected behavior
No
Could not load config file
iSponsorBlockTV server (please complete the following information):
Appreciate any help here. Seems so simple, yet...
The text was updated successfully, but these errors were encountered: