Make YAMS Your Own! 🚀

Want to add more containers to your YAMS setup? Maybe a cool new app you found, or something specific for your needs? No problem! YAMS makes it super easy to expand your media server with custom containers.

The Basics 📚

When you install YAMS, it creates two important files:

docker-compose.yaml: This is YAMS’s brain! Don’t modify this file directly.
docker-compose.custom.yaml: This is your playground! Add all your custom containers here.

Getting Started 🎯

First, let’s find your YAMS installation. I’ll use /opt/yams in these examples, but replace it with your actual install location:

cd /opt/yams

The Magic Variables ✨

YAMS provides some handy environment variables you can use in your custom containers:

PUID: Your user ID
PGID: Your group ID
MEDIA_DIRECTORY: Your media folder location
INSTALL_DIRECTORY: Your YAMS installation location

These make it super easy to keep your custom containers working in harmony with YAMS!

Let’s Add a Container! 🎮

Let’s walk through an example by adding Overseerr - a fantastic request management app for your media server.

First, open docker-compose.custom.yaml:

nano docker-compose.custom.yaml

If this is your first custom container, you’ll need to uncomment the services: line. Your file should start like this:

services:  # Make sure this line is uncommented!

Now let’s add Overseerr with all the YAMS goodies:

  overseerr:
    image: lscr.io/linuxserver/overseerr:latest
    container_name: overseerr
    environment:
      - PUID=${PUID}               # Using YAMS's user ID
      - PGID=${PGID}               # Using YAMS's group ID
    volumes:
      - ${INSTALL_DIRECTORY}/config/overseer:/config  # Using YAMS's config location
    ports:
      - 5055:5055
    restart: unless-stopped

Time to start your new container:

yams restart

You should see something like:

 ⠙ overseerr Pulling                                                                     5.2s
[...]

That’s it! Your new container is up and running! 🎉

Pro Tips 🎓

1. Container Discovery

Looking for cool containers to add? Check out:

linuxserver.io fleet (Highly recommended!)
Docker Hub

2. Network Magic 🌐

All containers in your docker-compose.custom.yaml automatically join YAMS’s network! This means they can talk to each other using their container names as hostnames.

For example, if you need to connect to Radarr from a custom container, just use http://radarr:7878 as the URL.

3. VPN Access 🔒

Want your custom container to use YAMS’s VPN? Add this to your container config:

    network_mode: "service:gluetun"

Check out Running Prowlarr behind the VPN for a detailed example!

4. Variable Power 💪

You can access any environment variable from YAMS’s .env file in your custom containers. Just use the ${VARIABLE_NAME} syntax!

Common Gotchas 🚨

Container Names: Make sure your custom container names don’t conflict with YAMS’s built-in containers.
Port Conflicts: Double-check that your new containers don’t try to use ports that are already taken.
Permissions: If your container needs to access media files, remember to use PUID and PGID!

Need Ideas? 💡

Here are some popular containers that work great with YAMS:

Overseerr or Petio: Let users request movies and shows
Tautulli: Advanced Plex monitoring and statistics
Organizr: Create a sleek dashboard for all your services

Need Help? 🆘

If you run into any issues:

Check our Common Issues page
Visit the YAMS Forum
Join our Discord or Matrix chat

Remember: YAMS is all about making your media server work for YOU. Don’t be afraid to experiment and make it your own! 😎

Advanced

Adding your own containers to YAMS