Another Docker Home Media Server

Good afternoon Habr. Writing this article encouraged me to close ex.ua and fs.to resources that are quite well-known in UA-IX. Since the valiant law enforcement officers did not bother to provide any worthy alternative, it was decided to take the process in hand, moreover, I had long wanted to organize a home storage / file storage facility not dependent on external providers. In the process of implementation, quite a lot of different systems were tried, but in the end everything was built that way, and not otherwise. The opinion is subjective, the implementation is available. The article itself is designed for beginners who need just a working solution, or for those who are thinking about their media server, but have not yet decided on implementation.



So the decision is made, let's begin.

Iron

The selection criteria were quite simple: compactness, normal work with WiFi, silence. After studying the iron market, the choice of which now provides the most extensive opportunities, there are several candidates left. Namely - HP MicroServer G8, ASUS VivoMini VC65R, and of course Rapsberry Pi 3.



After studying the available software to create a media server, it was decided to focus on ASUS VivoMini VC65R, since Rapsberry, which is based on ARM, does not support transcoding, and the available MicroServer options were equipped with a fairly old Celeron G1610T, which could not provide sufficient performance. So, the VC65R and 4xSamsung ST1500LM006 1.5TB were purchased.

')

operating system

On the one hand, there are quite a number of specialized distributions on the market, such as FreeNAS, NAS4Free, OpenMediaVault, and Rockstor. On the other hand, I would like to fully control the system, and if possible not use unnecessary services. So the choice was on Ubuntu Server 16.04 LTS. In general, the resulting configuration due to Docker does not depend on the operating system, but some services are somehow tied to the distribution, so if you want to repeat this configuration, keep this in mind.



The following directory structure was selected for file organization:

/ data - separate logical volume for storing media data and backups

/ data / Media - media data

/ data / TimeMachine - TimeMachine backups

/ opt / mediacenter - separate logical volume for storing service data

The installation process itself is not worth describing, since it depends on the distribution kit you choose, the only caveat is that since it would be nice to work with files without worrying about access permissions, we will give our user access using setfacl

apt-get install acl setfacl -Rm u:<username>:rwx /data setfacl -Rm d:u:<username>:rwx /data setfacl -Rm u:<username>:rwx /opt/mediacenter setfacl -Rm d:u:<username>:rwx /opt/mediacenter 

Software

So, what requirements can we set for such a media server, given the fact that there is a wide range of hardware under Mac OS X, iOS, Windows, and Android:



- Storage for TimeMachine + share for Mac OS X

- Shared resource for Windows

- Torrent client

- Monitoring updated torrents

- Personal cloud storage

- Media Server



Let's start in order.

Storage for TimeMachine + share for Mac OS X

The installation is very trivial, as well as everything described below.

 apt-get install netatalk avahi-daemon 

With this command, we install the open source implementation of the AppleTalk protocol and Bonjour. Now it only remains to export the / data / Media directory as an available share, and the / data / TimeMachine directory as available for the TimeMachine backup.



To do this, edit the file /etc/netatalk/AppleVolumes.default by adding at the end

 /data/TimeMachine "TimeMachine" cnidscheme:dbd options:tm,upriv,usedots volsizelimit:300000 allow:<username> /data/Media "Media" cnidscheme:dbd options:upriv,usedots dperm:0776 fperm:0666 allow:<username> 

To limit the space available to TimeMachine, an option is added.

 volsizelimit:300000 

To restrict access to a specific user option added

 allow:<username> 

Windows share

Since I have Windows on my network, I also need Samba. Everything is super simple here, since there are a lot of manuals on using Samba on the network. Nevertheless, for completeness of the article:

 apt-get install samba smbclient 

And the contents of smb.conf

Torrent client and Monitoring of updated torrents and Personal cloud storage and Media Server

It was decided to merge these requirements into one part, since all this is implemented on the basis of docker compose, and in fact they are one file thanks to which everything can be started with one command. I will probably omit the installation of docker and docker-compose, since they do not constitute anything complicated and are sufficiently described on the docker website.



Let's start with the selected software:



As a torrent client, we will use relatively lightweight Transmission.



To monitor the updated torrents, two solutions were selected for testing that specialize in the Russian-speaking segment of the network, namely TorrentMonitor and Monitorrent. Now they both work on my media server, and as a result there will be one that will show itself in the most optimal way. By the way, the authors of both decisions are present at Habré.



We’ll use ownCloud as a personal dropbox. I'm not sure that this is exactly the solution that will suit me one hundred percent, but at this stage it suits me. Alternatively, you can use NextCloud, Pydio or Seafile. In fact, the choice is much wider and there are quite a few decent alternatives on the market.



We will use Plex as a media server. An alternative called Emby was also tested, but I didn’t like it.



For all of the above, there are already ready docker images, the only thing that I didn’t like was the TorrentMonitor image, so it was decided to write my own.





The repository itself is here.



UPD: My pull request in nawa / torrentmonitor was sudzhen, so the article is updated.



So, the images are ready, we will write docker-compose.yml



UPD2: For those who do not work DLNA, you can comment out the ports section and uncomment the network_mode: host











Now you need to create a directory structure for storing metadata and media data:

 mkdir -p /opt/mediacenter/{mariadb-data,monitorrent-db,owncloud-apps,owncloud-config,plex-config,plex-transcode,torrentmonitor-db,torrentmonitor-torrents,transmission-config} mkdir -p /data/Media/{Anime,Books,Documents,Downloads,Games,Home\ Videos,Movies,Music,ownCloud,Photos,Torrents,TV\ Shows} 

And for complete convenience, create a systemd service





Now we will execute:

 systemctl daemon-reload systemctl enable mediacenter systemctl start mediacenter 

Docker compose will download images from the docker hub and launch our services. Now they will be available at:



Plex : http: // <YOUR_IP>: 32400

Transmission : http: // <YOUR_IP>: 9091

TorrentMonitor : http: // <YOUR_IP>: 8080

Monitorrent : http: // <YOUR_IP>: 6687

ownCloud : http: // <YOUR_IP>: 8081



Well, everything seems to be up and running. Now you can start testing, for example, save the .torrent file to the Torrents directory. Transmission should start the download, and soon the downloaded files will appear in the Downloads / complete directory.



Now there is the last step, to facilitate the work of the media server to recognize downloaded movies / TV shows / music. To do this, use a great product called FileBot which can rename files based on information from open sources like TheTVDB.



Installation is simple:

 apt-get install openjdk-8-jdk mediainfo openjfx wget -O filebot_4.7.5_amd64.deb http://downloads.sourceforge.net/project/filebot/filebot/FileBot_4.7.5/filebot_4.7.5_amd64.deb?r=http%3A%2F%2Fwww.filebot.net%2F&ts=1482609251&use_mirror=heanet dpkg -i filebot_4.7.5_amd64.deb 

Well, for convenience of renaming, we will write a couple of aliases:





Now, for example, you can use the command to work with the series:

 series-test <PATH_TO_SERIES_DIR> 

If the result of the work does not suit us, we can modify the search conditions using the --q and --filter options. If the result of the work suits us, we execute the command:

 series-move <PATH_TO_SERIES_DIR> 

As a result, the files of our series will be in the directory / data / Media / TV Shows / Series Name. Well, if we work with development or want to continue the distribution, you can execute the command:

 series-hardlink <PATH_TO_SERIES_DIR> 

As a result, hardlinks in the / data / Media / TV Shows / Series Name directory will appear.



In general, such a trivial way how to quickly and painlessly make your media server.