Hacker News Reader

Comment by andyl | Hacker News Reader

I can't keep up with the churn. Will come back to Docker in a year or two to see if things have stabilized.

FWIW we add a lot of new features, but we break very few APIs. API stability is extremely important to us, so you can actually build stable things on Docker and trust that we won't break it down the road.

I've had APIs subtly break on me between at least 2 releases (I think it's actually 3, but one time may have been user error). The main culprits were changing the parameters which are passed on container creation vs on container start, and changing error messages/response codes.

Yes, we have changed response codes when the old ones were just wrong. Like returning a 500 when really it should be a 404, that kind of stuff.

As far as start/create params, these should not be changed at all, other than that you can pass the options that you could one only pass on start to create. If something has broken here, it was most likely a mistake and should be reported on GH. Even if we change the underlying configuration, we do version the API and make sure we are sending/receiving the same structs over the wire.

TLDR; if something broke in the API, please report.

If I understood parent's comment (or maybe I just interpreted to agree with my own point of view), the implication is that some people are punting on even getting started w/ Docker, because things are moving too quickly. You may not break API's, but if the best-practices I learn today are completely obsolete by this time next year, that's still a bummer.

Try using Docker in a production environment. :(

Reply on news.ycombinator.com