iSponsorBlockTV Not Working

[faaborrelli]

I'm not sure if it's just me, but after installing the iSponsorBlockTV Docker, nothing happens; I can't open it. I've tried mapping a port and running it in both bridge and host modes, but I'm unsure how to get it to work.

[rachids]

If I'm not mistaken, you have to use the terminal to connect to the container

[CowSkullBolo]

I'm not able to get this to work either. If anyone else was able to get this to work, can you please share the directions? After installing from the app store, it seems as though it is not able to find a config file. The same issue was mentioned on the dmunozv04 iSponsorBlockTV forum as well.

Edit
Here is what I did to get things working. I did not use the app from the TMC store.

1.) Open terminal. Make a directory for iSponsorBlockTV in your desired path. I have mine at /DATA/AppData/isponsorblocktv
sudo mkdir -p /DATA/AppData/isponsorblocktv

2.) Run setup. You will need to tailor your settings and enter your YouTube API code, which is found in settings in the YouTube app on the device you are using (AppleTV, Roku, etc)
sudo docker run --rm -it \ -v /DATA/AppData/isponsorblocktv \ --net=host \ -e TERM=$TERM -e COLORTERM=$COLORTERM \ ghcr.io/dmunozv04/isponsorblocktv \ --setup

3.) After you have finished with setup, run iSponsorBlockTV as a background service.
sudo docker run -d \ --name isponsorblocktv \ --restart=unless-stopped \ -v /DATA/AppData/isponsorblocktv \ --network=host \ ghcr.io/dmunozv04/isponsorblocktv

I have tested this with the most annoying ad bombarding channels and it's working well. I hope this is helpful for those that may be able to navigate in CasaOS but struggle with the inner workings of terminal and Linux.