Live data from Hacker News

Docker in Production: A retort

patrobinson.github.io

131–132 of 132 posts

Re: Docker in Production: A retort

#131

Earlier quoted context omitted.

I run several erlang/elixir applications in containers, it works just fine. I'm not sure why someone claimed it doesn't, but I suspect they didn't try very hard if they did have trouble.

Chokes under significant load, perhaps? Do your erl/iex apps receive much traffic?

My apps are handling events from devices, a great many of them, probably ~1k/sec. That said, it could certainly depend on the app.

Re: Docker in Production: A retort

#132
post #82

Earlier quoted context omitted.

The issue you are referring to happens only if the docker client version is newer than the docker daemon version. In the case where the client is older than the daemon, it has always worked. Thanks for bringing this issue up though, because we are currently working on a fix. Here is the PR: https://github.com/docker/docker/pull/27745 As for DOCKER_API_VERSION, it is possibly not well documented, but it is indeed pres…

The client will nearly always be newer, so that message will almost always show up. You'll update your laptop tools regularly, and only bump your infrastructure occasionally. How many versions has this been a problem? It's not thinking about things like this until (apparently) 11 days ago that give Docker haters such ammo. The UX of the entire ecosystem feels like an afterthought. Yes, it's been evolving rapidly, but…

That's a fair statement, especially with d4mac/d4win and auto-update.

Posting a pull request and thinking about a problem are two very different things. The project has chosen to err on the side of safety (ie, user asked for some feature to be used but it is silently ignored since it's connecting to an older daemon) in this regard. -- this is not the only problem to solve

Post reply on HN