IMO, "Boycott" is the wrong term here. This is making an argument that Docker is bad due to Docker-inherent technology decisions. If that's true, those are the reasons not to use it.
Boycotts are reasons to not use a product for external reasons. i.e. not buying an otherwise-awesome car because the manufacturer used slave labor in the past.
(I personally hate containers and am way more into hardware-assisted virtualization, but I'm an outlier, and this is orthogonal to whether "boycott" is the right term here.)
Though I agree in principal with what is trying to be said it's unfortunate that it's wrong in several places.
For instance, Docker doesn't enforce you to run a single process per container. It simply requires you to provide it with one root process. This is true for all *nix systems, if you wanted to you could give it /sbin/init (or busybox, or systemd, or a custom supervisor) and launch SSH, NTP and friends under that.
All true on the networking front, things really do suck there out of the box. I would recommend looking at flannel with the native VXLan backend to reduce said suckage.
The storage stuff is made somewhat ok by the ability to pass volumes or entire storage devices in, which is what you should be doing for anything performance sensitive.
I don't think the problems the OP mentioned will resolve. Docker is fairly opinionated and so are the authors of it.
If the shoe fits; use it. But Docker is not a 1 size fits all;
If the idea of trusting a ubuntu image that is debootstrapped from someone on the docker team huzzah
If the idea of not running being able to run apt-get upgrade and having up to date packages; does not bother you then Docker is for you.
> Note I use Docker and it pains me to keep using it. I feel like I could be trusting Jack the Ripper; or the Pope.
The problem is that as Docker hub doesn't support digital signing of images uploaded to it, you are always trusting docker as well as the provider of the image, as anyone who has access (authorised or unauthorised) to their platform can just change the image.
This I do not understand. For me, one of Docker's selling points is easily being able to deploy/move containers, even to my own hardware (if I am running the daemon).
Boycotts are reasons to not use a product for external reasons. i.e. not buying an otherwise-awesome car because the manufacturer used slave labor in the past.
(I personally hate containers and am way more into hardware-assisted virtualization, but I'm an outlier, and this is orthogonal to whether "boycott" is the right term here.)