[willemmali]

If I got it right, the points made in this article are:

* Docker breaks other software

* Docker breaks it own API at random points between major versions

* Documentation is incorrect

* The project's management is bad at working with the community

I was thinking of trying Docker, but I think I'll stick to LXC for now.

[tachion]

There are other things to try out as well, if you're into experimentation: FreeBSD's bare Jails[0], JetPack[1] (FreeBSD based AppC implementation) and iocage[2] (Docker-ish userland wrapper for Jails and ZFS). Give them a chance, it could be eyes opening experience, especially that FreeBSD/Jails are more powerful, stable and battle tested than bare Linux/LXC in my opinion.

[0] https://www.freebsd.org/doc/handbook/jails.html

[1] https://github.com/3ofcoins/jetpack

[2] https://github.com/iocage/iocage

[ninkendo]

It breaks its own api in minor versions, actually. There hasn't been a major version since 1.0.

[mattkrea]

I think that is what the op meant. Between major versions meaning breaking changes happening in updates happening between 1.0 and 2.0 i.e. 1.1, 1.2, etc.

That said.. is Docker using semver? It doesn't look that way so is it written somewhere that this is breaking some standard?

[timthelion]

@mattkrea honestly, it never occured to me if Docker uses semver. I had simply assumed that it did :P

[mattkrea]

I have to admit my use of Docker is quite a bit different than yours and while I definitely understand the concerns / complaints if they aren't using it can we really be made if there are changes like this?

I only use Docker on AWS Elastic Beanstalk and they only update for security issues most often (Beanstalk is using 1.6 as I type this).

If I recall even the config file format changes between 1.6 and 1.7