1·
4 days agook. my reality have been truly checked! i havnt been thinking much about that type of thing, but yea we have definitely put ourselves in a terrible position.
everything that has happened since the 90s… using email for communication, everyone switching to using the cloud for nearly everything, i havnt stepped foot in a bank in 15+ years, so many things rely on computers and the internet now… what happens when most of that stops working!?
theres a lot of scrambling right now with countries trying to get their military back up to speed. let’s hope this is something that gets just as much attention.
where do you even start though lol?
good answers already so i will give you a different example.
my basic understanding of it is that docker was created originally for developers. im not sure if anyone planned for it to be a way to package up software for end users.
before docker existed you would have this issue where devs would be working on an app, say jellyfin, but each dev might be on a different platform (windows, mac, linux), or be using a different OS version, or different versions of whatever software… which meant it happened often that the app would work for one dev but not another. maybe one dev updated C# to version 2.3 and told everyone else to update, but someone missed the memo and is still running version 2.2 and now jellyfin wont work for them and time would be wasted trying to figure out where the mismatch was
so docker was a way to fix that “version hell” problem. every single thing that is needed for the app to run is kept inside the container. one dev will update something to a new version, then that container is shared to all other devs and each dev only has to worry about updating to the newest container before they start working on something.
app settings are kept in a separate location and the app data in another. in the case of jellyfin, the app data would be the movies or tv shows folder for example. then when you start the docker container, it will symlink those 2 locations/folders inside the container and the jellyfin app can access them as if they were folders that were actually stored inside the container.
so having the settings and data separate like that makes it very easy to update the container to a new version, or for a developer is probably useful being able to rollback to an older container for testing. its similar to how say windows puts the program files in one location and settings in the appdata folder
for end users its handy if theres a new version of jellyfin or whatever that isnt released yet but you want try it out, you can run 2 containers at the same time and both of them can access the same settings and data. (maybe with the newer one in read-only mode so it doesnt mess up your settings or data!)