Boycott Docker

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.)

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.

    Docker is vendor lock-in technology

The problems stated can and will be resolved as they evolve.

Personally, I use freebsd jails which is much better than docker. But if someone wants to use Docker, why not?

Regardless, I don't feel like containerization is not going anywhere.

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.