anyone used AI to help set up radarr/sonarr/overseerr..

quote:

---

No because is easy af to setup

What are you going to run them on?

---

dude i even messed up my docker installation

so i gotta start back over; i tried to set up a dashboard in docker for 6 years worth of fitbit data and messed up all kinds of permissions and shite.

so yes, i need someone to guide me like i'm TWELVE in setting al lthis up.

this is on my dell 3650 that's running nothing but plex right now (and threadfin)

quote:

---

why complicate it with docker? Plex is easy to setup with a repository install or .deb file.

---

because i know nothing about those add-ons and assumed by the brief research i did that you want to use docker to set them all up.

I have mine running in an LXC. I used this install script - LINK

quote:

---

huh?

Docker run xxxxxx


All you gotta do

---

my first project involved downloading 6 years of archived fitbit data, pulling it into a dashboard, connecting to the fitbitt API to pull new data as it comes in and formatting the dashboard so the data reporting is what i wanted.

so my first foray into docker was a little more complex and i had some issues when i installed it because i think i gave it too many 'admin' rights so i'm going to delete it and start over.

I used AI to learn what i needed for Docker, and now my arr/plex stack is all containers. There's trial and error but its a good learning tool as well. If you're setting up on physical machine shite aint that hard, but AI will definitely help

I guess I'm too old school to sacrifice the efficiency of proper installs vs the "ease" of trying to go to dockers/containers.

quote:

---

You lose maybe 1-2% performance and gain loads of time and sanity while doing upgrades, backups, and hardware migrations

---

It isn't just speed, it is the size of the total install on the drive. You end up with many copies of the same dependencies and have to rely on docker developers to use proper, updated dependencies. They make sense for people continually spinning up VMs all the time and taking them back down or even just for developers who need to constantly test changes.

For the person with a single linux PC in their home? Nah.

I enter one command and everything updates from repositories automatically. Seems much more simple.

Differences in sizes are not trivial. The few apps I tested were under 20MB on their own but the containers were more than 5x larger.

quote:

---

I enter one command and everything updates from repositories automatically. Seems much more simple. Differences in sizes are not trivial. The few apps I tested were under 20MB on their own but the containers were more than 5x larger.

---

I put off docker WAY too long in favor of VMs. I was so wrong. Docker is infinitely more resource efficient and an extremely organized way to keep software. Now for each machine it’s just /srv/[list,of,app-groups]/[group-list]-data and that’s my essentially entire directory tree that I ever use. Each app group gets its own docker-compose.yml and each individual app has one or two binds for data. Want to find a config? no /etc searching it’s just right there in that data folder.

Want to change machines?, just rsync the data directory binds and copy and paste (or rsync) the compose and you’re done. No dependencies except host drivers and docker itself.

You want to move a VM? sure it’s one file, but you’re stuck with a hypervisor forever.

Edit: docker containers can also be moved from x86 to arm64 with ease. Just replace the image path in docker-compose.yml.

Networking can get complicated but you’ll mostly just bind access ports 1:1. All AI chat bots know docker very well but none will correctly configure arrs or other self-hosted stuff unless fed the correct documentation.