+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228)
+---- Thread: Release Headless Kodi Docker Container (/showthread.php?tid=370583)
RE: Headless Kodi Docker Container - KillerKelvUK - 2024-11-05
(2024-11-03, 15:16)KillerKelvUK Wrote: Hey, thanks for the work with this. I'm up and running in docker and I think I have library updates sorted with the library watchdog addon. However in the web ui every minute its reports "Lost websocket connection" along with "Attempting websockets reconnect".FWIW, also amend Chorus2's Websockets port value at /#settings/web if not using the standard port value 9090, this stopped the errors.
I've tested connectivity with Kore and its happy, and using the web UI its fully functional from what I can see and I cannot find anything in the logs about these messages. Is this normal behaviour or am I looking in the wrong place?
Thanks
RE: Headless Kodi Docker Container - xbmcuser101 - 2024-11-22
I use multiple profiles for kodi. Does this support that? I am not seeing anywhere to select a profile to use.
RE: Headless Kodi Docker Container - bossanova808 - 2024-11-23
Yep so rather than faff about with trying to use multiple profiles in one container, which I suspect will be very hard work (how do you tell it to e.g. switch profiles when it needs to?), just run two containers and take care with your ports. (Indeed with both my containers I offset the ports as I have something else on 9090).
Then all you have to do is point various things at the right instance and bob's your uncle. E.g. in something like Sonarr you can use tags for various shows, then in the Connections bit, you can tell it which instance to contact when a new show has arrived etc. It works a treat and means your libraries are always up to date when you want them to be...
Here's my compose:
Code:
# KODI HEADLESS
# Both:
# https://github.com/matthuisman/docker-kodi-headless
# https://hub.docker.com/r/linuxserver/kodi-headless/
kodi-adults:
container_name: kodi-adults
image: matthuisman/kodi-headless:Omega
depends_on:
db:
condition: service_healthy
environment:
- PUID=${UID}
- PGID=${GUID}
- TZ=${TZ}
- KODI_DELAY=${KODI_DELAY}
volumes:
- ${KODI_ADULTS_CONFIG}:/config/.kodi:rw
# All offset by one to avoid LMS...
ports:
- 8081:8080 # WebUI
- 9091:9090 # Websockets
- 9778:9777 # esall interface port
restart: unless-stopped
kodi-kids:
container_name: kodi-kids
image: matthuisman/kodi-headless:Omega
depends_on:
db:
condition: service_healthy
environment:
- PUID=${UID}
- PGID=${GUID}
- TZ=${TZ}
- KODI_DELAY=${KODI_DELAY}
volumes:
- ${KODI_KIDS_CONFIG}:/config/.kodi:rw
ports:
- 8082:8080 # WebUI
- 9092:9090 # Websockets
- 9779:9777 # esall interface port
restart: unless-stopped
RE: Headless Kodi Docker Container - xbmcuser101 - 2024-11-23
Awesome Thanks! So I assume you're just running one DB and changing the name of the in the advanced setting file? Do you have a compose with maria db in it all in one or run them separate?
RE: Headless Kodi Docker Container - bossanova808 - 2024-11-23
Yep just the one DB with different names in as.xml - you could obviously do two DBs if you like, but it didn't seem worth the overhead to me.
And yes one compose with all my services (so db, db_backup (https://github.com/tiredofit/docker-db-backup) - 2 * kodi, and a few other services (nginx etc) for internal stuff. Those all run all the time.
I have a separate compose for ephemeral tools I use (beets, picard etc) with some aliases to start/stop those on demand.
Between those two composes, it covers everything I need currently, and is nice and simple and I know where to look for each type of thing...