Need Help with Docker Compose for My Media Server

0
4
Asked By TechSavvy001 On

Hey everyone! I'm really struggling with setting up my media server using Docker Compose and would love some help. I'm running Ubuntu and have spent quite a bit of time (over 12 hours now!) trying to get everything to work. I've written a .yml file with some help from ChatGPT and Google, but I'm still lost.

I got Gluetun to connect to Qbittorrent, which was my initial issue, but now Qbittorrent is working and nothing else seems to be. I specifically want only Qbittorrent to go through Gluetun—everything else should be separate. The logs for services like Sonarr and Radarr show no errors, but they say their web UIs are on `http://[::]:1234`, which I'm not sure is correct. Is that a placeholder for 'localhost'?

I also had a setup where my directories like Sonarr and Radarr were under `home/docker/media`, but now I can't seem to get them set up again. My Docker Desktop has `/mnt/` set up for shared directories, but I'm puzzled about why my volumes aren't populating like they should. Do I need to manually create those directories? Here's my current .yml setup. Any insights or tips would be appreciated!

4 Answers

Answered By CuriousCoder42 On

First off, good job on setting up Gluetun and Qbittorrent! For the logs showing `http://[::]:1234`, that's just a standard IPv6 representation, so it should work fine when accessed via 'localhost'.

TechSavvy001 -

Thanks for clarifying that! I was starting to second-guess everything.

Answered By DockerDude On

If you're looking for a smoother setup, check out the repo I linked. It's got a pretty straightforward compose file for a home media server. You might find it helpful!

Answered By MediaMaster102 On

You could also consider looking at r/mediastack. They offer some decent pre-configured setups that can get you rolling and help you learn Docker along the way!

Answered By GadgetGuru88 On

As for your directories, yes, you might need to create them manually if they're not being populated. Docker expects those paths to exist on your host machine. Check if they've been created under `/home/docker/media` as you defined in your .yml file.

TechSavvy001 -

Got it! I'll make sure to do that and see if it fixes the issue.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.