celedhrim / docker-kodi-server

Runs Kodi in headless mode with docker

Archive notice

This project is archived because kodi team no longer provides PPA. I recommend switching to matthuisman/docker-kodi-headless.

docker-kodi-server

Run Kodi using docker as a server

This will allow you to

• serves files through the Kodi UPnP Library to your UPnP client/players (such as Kodi or Chromecast).
• Web access every time , or use with some tools like htpc-manager
• Trigger library scan When you want using api or from sickbeard/sickrage/couchpotato/sonarr/radarr/...

Preqrequisites:

• Docker (Follow the installation instructions)
• A shared Library with mysql is higly recommended to shared library ( If you don't use UPnP)

Quick start

1. Prepare a full kodi profile with the regular GUI version ( windows or linux )

If you require web access, make sure to enable this, and set the port to 8089. Because 8080 is default for http proxy , this docker image expose 8089

Advices for the profile:

• You don't need any display , personnaly I disable all menu and told kodi to start on settings
• As software fake display is use , every graphic change is cpu cost , disable library update progess ( Settings / Media / Library : Hide progress of library updates)
• Only configure scrapers , and set addons on auto update

2. Make a copy of the ~/.kodi directory ( destination doesn't matter , this is just an example)

    $ cp -r ~./kodi ~/kodi-server-profile
   

3. Use prebuild docker image (see here)

For the last stable version,

    $ docker pull celedhrim/kodi-server

For a specific version,

    $ docker pull celedhrim/kodi-server:branchname

branchname	Kodi branch	Kodi version	Ubuntu version
lastest ( default)	nexus	20.1	22.10 (Kinetic Kudu)
helix	helix	14.2	14.04 (Trusty Tahr)
isengard	isengard	15.2	14.04 (Trusty Tahr)
jarvis	jarvis	16.1	16.04 (Xenial Xerus)
krypton	krypton	17.6	Archlinux
leia	leia	18.9	18.04 (Bionic Beaver)
matrix	matrix	19.4	18.04 (Bionic Beaver)
nexus	nexus	20.1	22.10 (Kinetic Kudu)
experimental	krypton	17.0rc2	18.04 (Bionic Beaver)

3. Run the image ( change the /path/to/kodi-server-profile)

    $ docker run -d --restart="always" --net=host -v /path/to/kodi-server-profile:/usr/share/kodi/portable_data celedhrim/kodi-server
   

   or if use specific branch

    $ docker run -d --restart="always" --net=host -v /path/to/kodi-server-profile:/usr/share/kodi/portable_data celedhrim/kodi-server:branchname
   

Build the container yourself

$ git clone https://github.com/Celedhrim/docker-kodi-server.git
$ cd docker-kodi-server
$ git checkout branchname
$ docker build --rm=true -t $(whoami)/kodi-server .

Then proceed with the Quick start section.

docker-kodi-server's Issues

19.3

can you kindly bump to 19.2 19.3? :)

docker unable to start after shutdown

I run this docker on unraid 6.8.3 (havent touched it in awhile).

At times if I stop the docker it doesnt shutdown cleanly and on tosses up the error about X server lock still existing.
Then with --restart="on-failure" set on the docker it will get stuck in restart loop.

# cat X.log

Warning: running as root
(EE)
Fatal server error:
(EE) Server is already active for display 100
	If this server is no longer running, remove /tmp/.X100-lock
	and start again.
(EE)
(EE)
Please consult the The X.Org Foundation support
	 at http://wiki.x.org
 for help.
(EE)
2021-05-07 16:01:28,952 Error: failed to connect to display :100
2021-05-07 16:01:28,952  could not connect to X server on display ':100' after 3 seconds
2021-05-07 16:01:28,952 killing xvfb with pid 25
2021-05-07 16:01:28,953 failed to kill xvfb process with pid 25:
2021-05-07 16:01:28,953  [Errno 3] No such process

I can edit the docker then start to 'fix' for that instance and it works fine.
Which I'm guessing is pruning out the tmp lock..

Testing this in controlled manner to replicate, docker is running.. now stopping via cli:

root@husky:/mnt/cache/appdata/.kodi# docker container ls
CONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS              PORTS                                                      NAMES
dd149d354daf        celedhrim/kodi-server:matrix   "/bin/kodi-run-wrapp…"   4 minutes ago       Up 4 minutes        0.0.0.0:8089->8089/tcp, 0.0.0.0:9090->9090/tcp, 9777/udp   kodi-server
b167c36001cd        linuxserver/mariadb            "/init"                  12 days ago         Up 6 minutes        0.0.0.0:3306->3306/tcp                                     mariadb

root@husky:/mnt/cache/appdata/.kodi# docker stop dd149d354daf
dd149d354daf

root@husky:/mnt/cache/appdata/.kodi# docker container ls
CONTAINER ID        IMAGE                   COMMAND             CREATED             STATUS              PORTS                    NAMES
b167c36001cd        linuxserver/mariadb     "/init"             12 days ago         Up 7 minutes        0.0.0.0:3306->3306/tcp   mariadb

Starting docker via unraid via unraid gui it shows 'started'. However looking at the cli I see its actually just in a restart loop:

root@husky:/mnt/cache/appdata/.kodi# docker container ls
CONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS                  PORTS                                                      NAMES
dd149d354daf        celedhrim/kodi-server:matrix   "/bin/kodi-run-wrapp…"   5 minutes ago       Up Less than a second   0.0.0.0:8089->8089/tcp, 0.0.0.0:9090->9090/tcp, 9777/udp   kodi-server
b167c36001cd        linuxserver/mariadb            "/init"                  12 days ago         Up 7 minutes            0.0.0.0:3306->3306/tcp                                     mariadb

root@husky:/mnt/cache/appdata/.kodi# docker container ls
CONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS                        PORTS                    NAMES
dd149d354daf        celedhrim/kodi-server:matrix   "/bin/kodi-run-wrapp…"   5 minutes ago       Restarting (1) 1 second ago                            kodi-server
b167c36001cd        linuxserver/mariadb            "/init"                  12 days ago         Up 7 minutes                  0.0.0.0:3306->3306/tcp   mariadb

...

root@husky:/mnt/cache/appdata/.kodi# docker container ls
CONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS                          PORTS                    NAMES
dd149d354daf        celedhrim/kodi-server:matrix   "/bin/kodi-run-wrapp…"   11 minutes ago      Restarting (1) 45 seconds ago                            kodi-server
b167c36001cd        linuxserver/mariadb            "/init"                  12 days ago         Up 13 minutes                   0.0.0.0:3306->3306/tcp   mariadb

and logs just show:

root@husky:/mnt/cache/appdata/.kodi# docker logs dd149d354daf
W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time.
W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time.
E: [pulseaudio] main.c: Daemon startup failed.
W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time.
E: [pulseaudio] main.c: Daemon startup failed.
W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time.
E: [pulseaudio] main.c: Daemon startup failed.

and trying to connect to docker fails

root@husky:/mnt/cache/appdata/.kodi# docker exec dd149d354daf ps -A
Error response from daemon: Container dd149d354daf124a869a2ccbd63fb6b8651b0f01cd1ab3c38f0ac5a94523223e is restarting, wait until the container is running

Leia Alpha 2 broken

The patch no longer works with Alpha 2. Work has been too busy to dig in, so hoping someone else may find some time.

segmentation fault on startup

I do get an segmentation fault on startup

root@fedora-anubis /home/zarathustra # docker run --net=host -v /root/kodi-server-profile/opt/kodi-server/share/kodi/portable_data --rm -it celedhrim/kodi-server bash                                                                        
root@fedora-anubis:/# ./opt/kodi-server/lib/kodi/kodi.bin --headless --no-test --nolirc -p
ASegmentation fault (core dumped)

linuxserver/kods-headless seems to be affected too
http://lime-technology.com/forum/index.php?topic=42439.0

Kodi v20

Kodi v20 is out, can we get a bump 😉

X.log -- Error setting up server dbus instance

do you also see dbus crashing in X.log after starting up pulseaudio?

2020-02-03 20:22:53,136 dbus server error
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_common.py", line 12, in dbus_exception_wrap
    v = fn()
  File "/usr/lib/python2.7/dist-packages/xpra/x11/server.py", line 1366, in make_dbus_server
    return X11_DBUS_Server(self, os.environ.get("DISPLAY", "").lstrip(":"))
  File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_server.py", line 38, in __init__
    session_bus = init_session_bus()
  File "/usr/lib/python2.7/dist-packages/xpra/dbus/common.py", line 22, in init_session_bus
    _session_bus = dbus.SessionBus(private=private)
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 211, in __new__
    mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 122, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
2020-02-03 20:22:53,138 Error setting up server dbus instance:
2020-02-03 20:22:53,138   org.freedesktop.DBus.Error.Spawn.ExecFailed
2020-02-03 20:22:53,138   /usr/bin/dbus-launch terminated abnormally without any error message

Scan Video Libray

I don't know why it doesn't scrape new movies. Can you look at some log to see the failure?

19.4 - dockerhub

just fyi looks like you never pushed out update to dockerhub when you updated to 19.4

Unable to open database: MyVideos119 [2026](SSL connection error: unknown error number)

I'm having trouble connecting to MySQL from kodi in the container. In the kodi.log it has a line like the following for every database version:
ERROR : Unable to open database: MyVideos119 [2026](SSL connection error: unknown error number)

After running docker exec /bin/bash in the container, I did apt install mysql-client from within the container and was able to connect successfully using the ip 10.8.0.xxx.

I tried running update-ca-certificates from within the container and that didn't help with kodi.

The .kodi (portable_data) directory was copied from an Ubuntu version 20.04 system and I know this build is 18.04. I didn't think that would be an issue, but is it? Any ideas anyone?

(I've upgraded all my x86_64 18.04 systems to 20.04.) Thanks!

Cant access http port

For some reason i cant access the webport:
Here is what i have:

kodi-server-profile/userdata/guisettings.xml

 <webserverport>8089</webserverport>

docker ps

CONTAINER ID        IMAGE                          COMMAND                CREATED             STATUS              PORTS               NAMES
e96e2a400495        celedhrim/kodi-server:latest   "/opt/kodi-server/li   4 minutes ago       Up 4 minutes                            modest_wozniak

/kodi-server-profile/userdata# netstat -tulp | grep kodi
tcp        0      0 *:1928                  *:*                     LISTEN      30100/kodi.bin
tcp6       0      0 [::]:9090               [::]:*                  LISTEN      30100/kodi.bin
udp        0      0 *:8881                  *:*                                 30100/kodi.bin
udp        0      0 *:1900                  *:*                                 30100/kodi.bin
udp        0      0 *:15165                 *:*                                 30100/kodi.bin
udp        0      0 *:7728                  *:*                                 30100/kodi.bin
udp6       0      0 [::]:9777               [::]:*                              30100/kodi.bin

Someone a idea? How does a working installation looks like?

Unable to build for aarch64

Trying to build for Pine64.

First it fails trying to install kodi because it tries to install 2:19.0* but the ppa has only 2:19.1* now. Once fixing it i then have

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 kodi : Depends: libshairplay0 but it is not installable
        Recommends: i965-va-driver but it is not installable
        Recommends: kodi-peripheral-joystick but it is not installable
        Recommends: kodi-inputstream-adaptive but it is not installable
        Recommends: kodi-inputstream-rtmp but it is not installable
E: Unable to correct problems, you have held broken packages.
The command '/bin/sh -c apt-get update &&     apt-get install -y pulseaudio xpra software-properties-common &&     add-apt-repository -y ppa:team-xbmc/ppa &&     apt-get install -y kodi=2:19.1* &&     apt-get clean &&     rm -rf /var/lib/apt/lists /usr/share/man /usr/share/doc &&     chmod +x /bin/kodi-run-wrapper.sh &&     mkdir /usr/share/kodi/portable_data' returned a non-zero code: 100

bump to 18.9

18.9 - https://kodi.tv/article/kodi-leia-189-release

kodi 19.0a1 - tested?

just was curious if you've tested kodi 19.x with this setup

master <> leia out of sync

while the dockerfile looks to be in sync (what matters), the :leia/readme was not updated to reflect its 18.5 now

xvfb won't run on lot's of devices

Get errors like 'Failed to get size of gamma for output screen' when using on headless devices (cloud server / openmediavault etc)

RAR and ZIP support ?

Hi,

seems that this kodi server build doesn't support rar and zip files. Would be cool if you add it.

GeminiServer

push patch to official Kodi?

I wonder why the headless patch is not in the official Kodi repo rather than having to do a build-from-source every time, just to apply that patch.

Are the Kodi dev's rejecting the patch and/or idea of a headless mode?

Alternatively, have you considered having Kodi start with a GUI in an Xvfb or something?

kodi v18 beta1 -- update?

curious to know if xbmc/xbmc#14125 being included has made this even easier to become headless as less things should need patching (assuming your using gdm build)?

Trying to clean via api hangs

When trying to use curl to make the headless kodi container clean the db, curl hangs and the db doesn't get cleaned. It may be trying to prompt something in the UI?

curl --data-binary '{ "jsonrpc": "2.0", "method": "VideoLibrary.Clean", "id": 1}' -H 'content-type: application/json;' http://kodi:kodi@localhost:8085/jsonrpc

kodi.log output:
18:01:28.467 T:139835964626688 INFO: Platinum [neptune.http]: NPT_CHECK failed, result=-20014 (NPT_ERROR_TIMEOUT) [(result)]
18:01:29.985 T:139836549469952 DEBUG: CWebServer[8080]: request received for /jsonrpc
18:01:29.985 T:139836549469952 DEBUG: CWebServer[8080] [IN] HTTP/1.1 POST /jsonrpc
18:01:29.985 T:139836549469952 DEBUG: CWebServer[8080] [IN] Accept: /
18:01:29.985 T:139836549469952 DEBUG: CWebServer[8080] [IN] Authorization: Basic a29kaTprb2Rp
18:01:29.985 T:139836549469952 DEBUG: CWebServer[8080] [IN] Content-Length: 60
18:01:29.985 T:139836549469952 DEBUG: CWebServer[8080] [IN] Host: localhost:8085
18:01:29.985 T:139836549469952 DEBUG: CWebServer[8080] [IN] User-Agent: curl/7.47.0
18:01:29.985 T:139836549469952 DEBUG: CWebServer[8080] [IN] content-type: application/json;
18:01:29.985 T:139836549469952 DEBUG: JSONRPC: Incoming request: { "jsonrpc": "2.0", "method": "VideoLibrary.Clean", "id": 1}
18:01:29.992 T:139837173213376 NOTICE: CleanDatabase: Starting videodatabase cleanup ..
18:01:29.992 T:139836560041728 DEBUG: CAnnouncementManager - Announcement: OnCleanStarted from xbmc
18:01:29.992 T:139837173213376 DEBUG: Mysql Start transaction
18:01:48.532 T:139836524291840 DEBUG: Thread AESinkNull 139836524291840 terminating
18:02:18.516 T:139835964626688 INFO: Platinum [neptune.http]: NPT_CHECK failed, result=-20014 (NPT_ERROR_TIMEOUT) [(result)]

I never have an issue doing a db update with curl, so I'm not sure what to try to fix it.

curl --data-binary '{ "jsonrpc": "2.0", "method": "VideoLibrary.Scan", "id": 1}' -H 'content-type: application/json;' http://kodi:kodi@localhost:8085/jsonrpc

docker usage/size - sanity check

not sure if this is normal sizes, after 24 hours:
~ confirmed no runaway log file in the docker

docker images

# docker images
REPOSITORY                  TAG                 IMAGE ID            CREATED             SIZE
celedhrim/kodi-server       leia                41ba4699498c        7 weeks ago         648MB

docker stats

CONTAINER ID        NAME                CPU %               MEM USAGE / LIMIT     MEM %               NET I/O             BLOCK I/O           PIDS
feca3fdc6b9c        kodi-server         2.65%               778.1MiB / 3.739GiB   20.32%              468MB / 8.18MB      694MB / 86.2MB      35

actually looks like the size is normal per:

docker history  celedhrim/kodi-server:leia 
IMAGE               CREATED             CREATED BY                                      SIZE                COMMENT
41ba4699498c        7 weeks ago         /bin/sh -c #(nop)  ENTRYPOINT ["/bin/kodi-ru…   0B                  
<missing>           7 weeks ago         /bin/sh -c #(nop)  EXPOSE 8089/tcp 9090/tcp …   0B                  
<missing>           7 weeks ago         /bin/sh -c apt-get update &&     apt-get ins…   583MB               
<missing>           7 weeks ago         /bin/sh -c #(nop) ADD file:5e71211e48456c10c…   199B                
<missing>           7 weeks ago         /bin/sh -c #(nop)  ENV DEBIAN_FRONTEND=nonin…   0B                  
<missing>           7 weeks ago         /bin/sh -c #(nop)  MAINTAINER celedhrim "cel…   0B                  
<missing>           2 months ago        /bin/sh -c #(nop)  CMD ["/bin/bash"]            0B                  
<missing>           2 months ago        /bin/sh -c mkdir -p /run/systemd && echo 'do…   7B                  
<missing>           2 months ago        /bin/sh -c set -xe   && echo '#!/bin/sh' > /…   745B                
<missing>           2 months ago        /bin/sh -c [ -z "$(apt-get indextargets)" ]     987kB               
<missing>           2 months ago        /bin/sh -c #(nop) ADD file:a48a5dc1b9dbfc632…   63.2MB 

Websocket & xpra attach & UID

Hi .. I've got 3 questions:

1.) Why isn't the websocket port (9090) exposed?
2.) Would it be possible, if xpra is running anyways, to enable "xpra attach" via ssh or tcp?
3.) It's not possible to run the container with something like "--user 1000:1000". Would be nice to be able to!

Thx

Somehow it doesnt start

So I set up the docker image.
And docker deploys the image but it doesnt start and docker logs show the following:

W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time.
E: [pulseaudio] main.c: Daemon startup failed.

At the same time i wonder why it needs pulsaudio. Does it need this even if it is headless?

What am i doing wrong?
Can someone please share an example setup in docker?

High CPU and Ram on Synology NAS

Hey

I've just run the container and without it doing anything special, I'm seeing constant 11%-15% CPU and 1.2GB of RAM usage.

Is that normal behavior ?

Nexus branch not working

The Matrix branch had been working great.
Upgraded to Nexus (to match other installs on the network), and it fails to start.

Tried a fresh install (empty profile, new container), same thing.

There are some errors on X.log that I don't know if are normal or not, but eventually the kodi.log reaches an infinite loop of this:

2023-03-19 20:00:58.223 T:153      info <general>: CActiveAESink::OpenSink - initialize sink
2023-03-19 20:00:58.223 T:153     error <general>: CActiveAESink::OpenSink - no sink was returned
2023-03-19 20:00:58.223 T:152     error <general>: ActiveAE::InitSink - returned error

I've attached both files, from a completely fresh install.
Let me know if there's anything else that could be useful.

kodi.log

X.log

Regular segfault with krypton

I see this in syslog:

[1717403.570932] kodi.bin[26471]: segfault at 0 ip 000055610c63055b sp 00007ffc1dab7090 error 4 in kodi.bin[55610b974000+12d1000]

I use this docker image on my homeserver to get access to the WebUI of Kodi and listing to music. Unfortunately as kodi segfaults and restarts the connection to the WebUI drops.

I added the fix from #7 as a PR: #11

@Celedhrim Than i noticed you already working on Leia support, is there more to improve at the headless patch?

Any plans for arm / raspberry support?

Hello I tried building tend dockerfile and running in to several issues as below. Any chance you can add arm to this or is this not possible? If any help needed to compile in Pi I can help. Let me know, thanks

The following packages have unmet dependencies:
kodi : Depends: kodi-x11 (< 2:18.6+git20200301.0802-final-0bionic.1~) but it is not installable
Depends: libshairplay0 but it is not installable
Recommends: i965-va-driver but it is not installable
Recommends: kodi-peripheral-joystick but it is not installable
Recommends: kodi-inputstream-adaptive but it is not installable
Recommends: kodi-inputstream-rtmp but it is not installable
E: Unable to correct problems, you have held broken packages.
The command '/bin/sh -c apt-get update && apt-get install -y pulseaudio xpra software-properties-common && add-apt-repository -y ppa:team-xbmc/ppa && apt-get install -y kodi=2:18.6* && apt-get clean && rm -rf /var/lib/apt/lists /usr/share/man /usr/share/doc && chmod +x /bin/kodi-run-wrapper.sh && mkdir /usr/share/kodi/portable_data' returned a non-zero code: 100

Suggestions for instructions

I want to suggest a few edits to the docs:

The following command is ambiguous - the results depend on the state of the system:
cp -r ~/.kodi ~/kodi-server-profile

If ~/kodi-server-profile is an existing directory, then the above command creates a directory .kodi inside it.
Otherwise, the command creates a directory named ~/kodi-server-profile containing the contents of ~/.kodi. I found by trail and error that the second is the one that's needed.

Also, docker inspect name shows that port 8089 is exposed. This is close to but different from the standard web app port of 8080. So, the user is required to manually edit the kodi config to match the exposed port, which requires some digging. Suggested edits:

"

1. Prepare a full kodi profile with the GUI version. If you require web access, make sure to enable this, and set the port to 8089.
2. Make a copy of the ~/.kodi directory: cp -r ~./kodi ~/kodi-server-profile
   "

thumbnails always re-cached and not shown over UPnP

Hi,

• thumbnails getting cached just fine in the thumbnails folder when browsing movies or music on the kodi-webserver-gui but they are not used and are re-cached when refreshing pages on the webserver - I can delete the folders within the thumbnail folder and/or the Textures13.db, the thumbnails folders fill up again but are always re-cached over and over again.
• maybe it has something to do with the first issue because thumbnails are not showed over UPnP

I'm using a full kodi setup on Ubuntu for the config folder - there everything is just fine (caching and thumbnails over UPnP

Can you reproduce this behaviour on your side?

could it be a reason of the headless patch?

Thank you

Run it from docker-compose

Hello celedhrim,
hello everyone!

I'm trying to get it running with docker-compose via Portainer, but with no success so far. Though no error messages in logs, the UPnP device does not show up. Loos like container does not check the "/path/to/kodi-server-profile".

Docker-compose yaml:

version: "2.1"
services:
  kodi-server:
    image: celedhrim/kodi-server
    container_name: kodi-server
    environment:
      - TZ=Europe/Berlin
      - PUID=1024
      - PGID=101
    volumes:
      - /volume1/kodi:/usr/share/kodi/portable_data celedhrim/kodi-server
    ports:
      - 8089:8089  # web access
    restart: unless-stopped

Container logs:

W: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set.
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling SHM mode.
N: [pulseaudio] main.c: Running in system mode, forcibly disabling exit idle time.

What do I miss? Any help appreciated :)