I mean, for anything where you’re willing to trust the container provider not to push breaking changes, you can just run Watchtower and have it automatically update. That’s how most of my stuff runs.
I mean, for anything where you’re willing to trust the container provider not to push breaking changes, you can just run Watchtower and have it automatically update. That’s how most of my stuff runs.
A while back I came to the conclusion that “games for experienced players only” shouldn’t be a thing that exists.
Roleplaying games are, at their heart, about sharing in a story together. At least, thats the version of them that I enjoy. And I’ve found time and again that people who know nothing about roleplaying games enjoy that too.
Enjoying stories isn’t something we need experience to do. We learn it as children. The storytelling part, that takes a little bit of learning, but if you do things right, if you run the game in the right way, and manage your players in the right way, you’ll find that learning process is very, very quick.
Roleplaying games should have a learning curve that’s measured in hours, not years. They should be for everyone, and if you do it right they are.
Personally, I always like to use containers when possible. Keep in mind that unlike virts, containers have very minimal overhead. So there really is no practical cost to using them, and they provide better (though not perfect) security and some amount of sandboxing for every application.
Containers mean that you never have to worry about whether your VM is running the right versions of certain libraries. You never have to be afraid of breaking your setup by running a software update. They’re simpler, more robust and more reliable. There are almost no practical arguments against using them.
And if you’re running multiple services the advantages only multiply because now you no longer have to worry about running a bespoke environment for each service just to avoid conflicts.
While I understand the frustration of feeling like you’re being forced to adopt a particular process rather than being allowed to control your setup the way you see fit, the rapid proliferation of containers happened because they really do offer astonishing advantages over traditional methods of software development.
I’ll add here that the “docker top” command allows you to easily see what kind of resources your containers are using.
If you prefer a UI, Dozzle runs as a container, is super lightweight, requires basically no setup, and makes it very easy to see your docker resource usage.
Ooh, I will be giving this a go!