Skip to content

Docker Image running a Twonky Server including ffmpeg

License

Notifications You must be signed in to change notification settings

H2CK/twonkyserver

Repository files navigation

Docker Pulls GitHub tag (latest by date)

docker-twonkyserver

TwonkyMedia server (TMS) is DLNA-compliant UPnP AV server software from PacketVideo. It runs on Linux, Mac OS X, Windows XP, Windows Vista, Windows Home Server, and Windows 7 computers as well as Android, iOS, and other mobile platforms. TwonkyMedia server can be used to share and stream media to most UPnP AV or DLNA-compliant clients, in addition to non-UPnP devices through the HTML, RSS, and JSON supported front ends. In this docker image beside the TwonkyMedia server also ffmpeg is included to allow thumbnail creation and stream transcoding. The includes ffmpeg is based on the the static builds from johnvansickle. The docker image is based on Ubuntu Bionic.

You will need a valid licence to run the TwonkyMedia server inside this docker image.

Usage

docker run -d --net=host --name=twonkyserver -v /path/to/config:/config:rw -v /path/to/data:/data:ro -v /etc/localtime:/etc/localtime:ro dtjs48jkt/twonkyserver

After starting the docker container go to:

http://server:9000/webconfig

Update Functionality

This docker image is based on Ubuntu. if you set -e UPDATE_ON_START=TRUE on each start of the container an update of the used Ubuntu packages is performed. Due to the running update it might take a little longer until the application TwonkyMedia server is available.

Parameters

  • -v /config - Where TwonkyMedia server stores its config files
  • -v /data - Where TwonkyMedia server will find the media to share via DLNA
  • -v /etc/localtime - Set to use the corect time setting with TwonkyMedia server
  • -e GROUP_ID for GroupID - see below for explanation
  • -e UPDATE_ON_START=TRUE enable auto update functionality on restart
  • --net=host Used to DLNA communication in the network

User / Group Identifiers

Sometimes when using data volumes (-v flags) permissions issues can arise between the host OS and the container. To avoid this issue you are allowed to specify the group GROUP_ID. Ensure the data volume directory on the host is owned by the same group you specify.

Versions

  • 13.09.2017: Initial release. Using phusion 0.9.22, TwonkyMedia server 8.4.1 and ffmpeg 3.3.4
  • 20.09.2017: Permission fix. Contains phusion 0.9.22, TwonkyMedia server 8.4.1 and ffmpeg 3.3.4
  • 24.10.2017: Added auto update functionality. Contains phusion 0.9.22, TwonkyMedia server 8.4.1 and ffmpeg 3.3.4
  • 24.11.2017: Update to phusion 0.9.22, TwonkyMedia server 8.5 and ffmpeg 3.4
  • 02.09.2018: Update to TwonkyMedia server 8.5.1 and ffmpeg 4.0.2
  • 07.09.2019: Update to TwonkyMedia server 8.5.1 and ffmpeg 4.2.1 / changed base image to Ubuntu Bionic (fixed update problems with phusion)
  • 06.01.2020: Update of base image to Ubuntu 20.04
  • 30.03.2021: Update to TwonkyMedia server 8.5.2 and ffmpeg 4.3.2