Trying to get Kitana up and running in docker with Portainer
alexander-paterson opened this issue · 8 comments
I've been using https://kitana.bas.sh/ for ages to use Kitana but for the last 4-5 days it's just been timing out.
So, I decided to try and try and get it up and running in Docker.
I created a Stack in Portainer and used the Docker-compose from the Kitana GitHub, my first issue was Portainer gave me an error saying Service kitana has a link service plex which is undefined.
I removed the links section and the container was created.
However, when I try to go to ip:31337 the page doesn't load.
Does anyone have any ideas on how to get Kitana running?
I seem to be having a similar issue.
Logs look ok and no error but the page just fails to load.
[02/Aug/2020:17:57:54] ENGINE Bus STARTING
[02/Aug/2020:17:57:54] ENGINE Starting SassCompilerPlugin
[02/Aug/2020:17:57:54] ENGINE Serving on http://0.0.0.0:31337
[02/Aug/2020:17:57:54] ENGINE Bus STARTED
[02/Aug/2020:17:57:54] Starting Sass Compile
[02/Aug/2020:17:57:54] SassCompilerPlugin: Compiling /app/static/sass to /app/static/css
[02/Aug/2020:17:57:55] ENGINE Listening for SIGTERM.
[02/Aug/2020:17:57:55] ENGINE Listening for SIGHUP.
[02/Aug/2020:17:57:55] ENGINE Listening for SIGUSR1.
Is there additional logs I could capture to help investigate this?
Did you upgrade to the "new Plex Movie agent"?
- https://forums.plex.tv/t/introducing-the-new-plex-movie-agent/615989
- https://user-images.githubusercontent.com/1359593/88648840-a72c7780-d0c7-11ea-9300-51872a1dc3bd.png
For me the problem startet after I did that.
Thay would stop the plugins from working on the new movie library when you try and use them, I wouldn't have thought that it would stop this external piece of software from loading.
I can open Kitana from Google Chrome in Incognito, so it must be an extension that gives the problem.
@unabatedshagie
You can try "ip:31337/kitana" that works for me.
@unabatedshagie
You can try "ip:31337/kitana" that works for me.
🤦♂️ That worked for me, thanks!
Using the host pc ip does not work.
I also tried the docker ip.
I was able to get kitana up and running in a python virtual env no problem but the docker version is having the same trouble.
Any additional logging or tests I can perform via a connection to the kitana docker instance?
Thay would stop the plugins from working on the new movie library when you try and use them, I wouldn't have thought that it would stop this external piece of software from loading.
It's the /Kitana in the command. Just change it to / and recreate your container.