What’s up, what’s down and what are you not sure about?
Let us know what you set up lately, what kind of problems you currently think about or are running into, what new device you added to your homelab or what interesting service or article you found.
Personally I’m finally reaping the fruits of my labour and enjoy my stable homelab without doing much. One node went down recently and the other took over until I restarted so I was not in a hurry to fix things. Enjoying family time and only running updates that aren’t automated (yet). I’m about to dig a bit deeper into logging, probably setting up central log collection like Loki at some point, but not yet.


I wanna get into it but man, the mountain of knowledge I need to even understand what people are talking about is hard to climb. I’m trying to just get some stuff running in docker and it fails to launch and I’m like… How?! Isn’t that the whole point of docker lol. Baby steps I guess
I’ve learnt it from scratch in my week off, spending 2 or 3 hours on it every night for a week (although this might be underselling it as I had become familiar with desktop Linux over the past year and had a superficial idea of Docker containers with my Synology NAS). But still it’s not as big a deal as you think once you find some good resources. I’m going to comment about my setup after this in this thread… Have a look.
Main resource that helped me was Marius Hosting and ChatGPT got me out of trouble when I got stuck by deciphering logs for me when things didn’t work.
Thanks. Yeah I’m just trying to work at it slowly in my downtime instead of just watching YouTube all night.
I felt exactly the same when i started - the learning curve is real! Try TrueCharts.org or linuxserver.io for reliable docker templates with good docs that actually work, saved me so much troubleshooting headache.
Thanks will do!
It’s messy. Dockers superpower: You can write a crazy ass python application that needs dozens of dependencies and weird software configured. You put it into a container, you can update and publish the container with a single script call. Other people can install that, set some variables and not have to install the dozens of other pieces of software. They also don’t have to worry about updates.
But that’s not to say you don’t have to worry about networks, storage and ports.
Then the simplicity of the configuration of containers depends upon the person that made the container. Maybe they wanted to be very flexible and there are dozens of things you need to set. Maybe they didn’t include the data store internally in that container and you need your own data store in another container.
Are you doing things through docker compose? If so, feel free to PM me or reply here with your compose file and I’ll help as best I can
Docker should be trivial to run. Hopefully it gives you some useful messages in the logs.