Version number / Beta version number / Update version number and when it whas released. 11-08-16: Rebase to alpine linux, move from lsiodev to lsiocommunity.Explanation: NEW SOFTWARE= New tool since your last visit NEW VERSION= New version since your last visit NEW REVIEW= New review since your last visit NEW VERSION= New version Latest version.17-09-16: Change transcode folder, thanks Kwull.14.10.16: Add version layer information.07.02.17: Compile ffmpeg for subtitles filter support ,consolidate layers.26.08.17: Use local copy of dcraw as dns issues on download server.26.11.17: Use cpu core counting routine to speed up build time, bump ffmpeg to 3.4.03.01.18: Deprecate cpu_core routine lack of scaling, bump ffmpeg to 3.4.1.18.08.18: Rebase to alpine 3.8 and use buildstage.To monitor the logs of the container in realtime docker logs -f serviio.ĭocker inspect -f '' lsiocommunity/serviio Versions Shell access whilst the container is running: docker exec -it serviio /bin/bash Setting a mapping for transcoding -v /transcode ensures that the container doesn't grow unneccesarily large. Uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)Īdd as many media folder mappings as required with -v /media/tv-shows etc. In this instance PUID=1001 and PGID=1001. Ensure the data volume directory on the host is owned by the same user you specify and it will 'just work' ™. We avoid this issue by allowing you to specify the user PUID and group PGID. Sometimes when using data volumes ( -v flags) permissions issues can arise between the host OS and the container. It is based on alpine linux with s6 overlay, for shell access whilst the container is running do docker exec -it serviio /bin/bash. -e PUID for UserID - see below for explanation.-e PGID for GroupID - see below for explanation.-v /transcode - Transcode folder - see below.-v /media - Path to your media files, add more as necessary, see below.-v /config - Where serviio stores its configuration files etc.-v /etc/localtime for timesync - optional.So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 would show you what's running INSIDE the container on port 80. For example with a port -p external:internal - what this shows is the port mapping from internal to external of the container. The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side.

Serviio 1.9 crack blogspot