I've started experimenting with Emby as an alternative to Plex, because of the advanced parental controls it offers. Based on my experimentation thus far, I have a "kid-safe" profile which automatically logs in, and only displays kid-safe content, based on ratings.
- Docker swarm cluster with persistent shared storage
- Traefik configured per design
- DNS entry for the hostname you intend to use, pointed to your keepalived IP
Setup data locations¶
We'll need a location to store Emby's library data, config files, logs and temporary transcoding space, so create /var/data/emby, and make sure it's owned by the user and group who also own your media data.
Create emby.env, and populate with PUID/GUID for the user who owns the /var/data/emby directory (above) and your actual media content (in this example, the media content is at /srv/data)
Setup Docker Swarm¶
Create a docker swarm config file in docker-compose syntax (v3), something like this:
I share (with my patreon patrons) a private "premix" git repository, which includes necessary docker-compose and env files for all published recipes. This means that patrons can launch any recipe with just a
git pull and a
docker stack deploy 👍
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
version: "3.0" services: emby: image: emby/emby-server env_file: /var/data/config/emby/emby.env volumes: - /var/data/emby/emby:/config - /srv/data/:/data deploy: labels: - traefik.frontend.rule=Host:emby.example.com - traefik.docker.network=traefik_public - traefik.port=8096 networks: - traefik_public - internal ports: - 8096:8096 networks: traefik_public: external: true internal: driver: overlay ipam: config: - subnet: 172.16.17.0/24
Setup unique static subnets for every stack you deploy. This avoids IP/gateway conflicts which can otherwise occur when you're creating/removing stacks a lot. See my list here.
Launch Emby stack¶
Launch the stack by running
docker stack deploy emby -c <path -to-docker-compose.yml>
Log into your new instance at https://YOUR-FQDN, and complete the wizard-based setup to complete deploying your Emby.
Chef's Notes 📓¶
- I didn't use an oauth2_proxy for this stack, because it would interfere with mobile client support.
- Got an NVIDIA GPU? See this blog post re how to use your GPU to transcode your media!
- We don't bother exposing the HTTPS port for Emby, since Traefik is doing the SSL termination for us already.
Tip your waiter (support me) 👏¶
Did you receive excellent service? Want to make your waiter happy? (..and support development of current and future recipes!) See the support page for (free or paid) ways to say thank you! 👏
Flirt with waiter (subscribe) 💌¶
Want to know now when this recipe gets updated, or when future recipes are added? Subscribe to the RSS feed, or leave your email address below, and we'll keep you updated. (double-opt-in, no monkey business, no spam either - check the archive for proof!)