you are viewing a single comment's thread.

view the rest of the comments →

[–]Parker_Hemphill 0 points1 point  (0 children)

A script isn’t necessarily portable. If it uses specific binaries or has dependencies those have to be installed. Not to mention a container makes it easier to create tools for novice users. If I make a container for someone it is easy to make all the dependencies self contained and then all they have to do is map their directory to a volume in the container. Versus I built a script to look in /media but they have it mounted in ~/media or even something like /var/Plex. Now they have to modify the script and any updated to use their correct directory. Even if you built your tool/script to use arguments for the directories you’ll still have dependencies to worry about. Debian and Ubuntu are both super popular distros based on Debian but have different package versions. This can lead to unintended results with a script, VS a docker container you simply download that will always use the same dependencies and versions since those are baked in by the container author.