The author clearly doesn't know how to use Docker and blames their issues on the tool and even on the concept of containerization !
Regarding a file system, in most docker containers you should be able to run "docker exec -ti <if> sh" and you have a shell inside the container, where you *have autocomplete*,and can *run linux commands like locate*.
Regarding configuration files, that's an application issue, 99% of applications I run with docker use configuration files, because that just how you manage software. So either your BTCPay thing doesn't have a configuration file, and it would be the same than if you didn't use Docker, or it has one and you didn't know you could mount it inside the container.
And regarding the "fake" reasons :
> It’s no easier to setup a Docker file than a installation shell script, even one that runs on multiple platforms.
Um, no ? Because between "knowing the environment my code runs in" and "not knowing the environment my code runs in" of course the first option is better and easier to reason about.
> Containers can only be “easier to manage” when they strip away all of the user’s ability to manage in the normal unix-way,
and that is relatively unmissed.
By unix way what do you mean ? The container is a process, you can manage the process the unix way.
The focus is in the process' environment, which is better if the end user *doesn't* have to manage it.
> Containerization makes software an opaque box where you are ultimately at the mercy of what graphical settings menus have been programed into the software. It is the nature of containers that bugs can never been fixed by users, only the official development team.
I think you just don't know how to use Docker to edit the files of your application, but it's really as easy as just editing files on linux because *the container is really just using a linux filesystem*
> People who do not know how to use Unix-based operating systems or specifically GNU/Linux.
Did you miss the fact that you need to know how to use linux to write a working Dockerfile ? Because it still runs linux !
Regarding a file system, in most docker containers you should be able to run "docker exec -ti <if> sh" and you have a shell inside the container, where you *have autocomplete*,and can *run linux commands like locate*.
Regarding configuration files, that's an application issue, 99% of applications I run with docker use configuration files, because that just how you manage software. So either your BTCPay thing doesn't have a configuration file, and it would be the same than if you didn't use Docker, or it has one and you didn't know you could mount it inside the container.
And regarding the "fake" reasons :
> It’s no easier to setup a Docker file than a installation shell script, even one that runs on multiple platforms.
Um, no ? Because between "knowing the environment my code runs in" and "not knowing the environment my code runs in" of course the first option is better and easier to reason about.
> Containers can only be “easier to manage” when they strip away all of the user’s ability to manage in the normal unix-way, and that is relatively unmissed.
By unix way what do you mean ? The container is a process, you can manage the process the unix way.
The focus is in the process' environment, which is better if the end user *doesn't* have to manage it.
> Containerization makes software an opaque box where you are ultimately at the mercy of what graphical settings menus have been programed into the software. It is the nature of containers that bugs can never been fixed by users, only the official development team.
I think you just don't know how to use Docker to edit the files of your application, but it's really as easy as just editing files on linux because *the container is really just using a linux filesystem*
> People who do not know how to use Unix-based operating systems or specifically GNU/Linux.
Did you miss the fact that you need to know how to use linux to write a working Dockerfile ? Because it still runs linux !