I used to just put my servers together with some systemd files and scripts. But I recently decided to finally follow the herd and do the docker thing.<p>It has been so frustrating for me. I get the supposed plus (encpasulation, isolation, etc), but I just had a build that regressed for reasons I can not figure out (it's just an Elixir Phoenix app with a timescaledb). Out of the blue, my db init scripts aren't running all of a sudden (I did apt update the servers).<p>I just find myself staring at so many layers of tools. We're a (very) small team and I just need tech that can be understood and managed and that I don't have to arguments with LLMs about how to diagnose/fix.<p>Is this just a rough spot, and I need to be cheered on and I'll eventually "get it all"? Or would I be better just using my oldtimer knowledge skills to set the thing up?
I would suggest you stick with it. Docker compose is very powerful once you get the hang of it and it can be used to deploy straight to AWS etc.<p>But no, you're not a bad person if you give up. Remember that each time you restart a container it goes back to it's original state. Apt update should be done during the image build.