News for hackers. Stuff that matters.
Re:Docker in Production: A retort by pmarreck on Saturday November 05, 2016 @04:04PM (#12881607)
Anyone know why Erlang doesn't run well on containerized Docker?
Re:Docker in Production: A retort by user5994461 on Sunday November 06, 2016 @06:50AM (#12884683)
Hello. It was a long time ago and I didn't get all the details.

I think it either came down to a broken version of docker at the time that couldn't run properly.

Or it was because of unstability from Docker. All our Erlang apps are meant to take thousands of requests per second and Erlang have particular ideas about how the system/network should behave. It's very hard on Docker and any unstability or incompatibly would make up for outstanding failures.

Either way, we know for sure now that there were many major critical issues with Docker at the time of the Erlang trial. Not adopting it was the right decision, and it still is.

We only use Erlang for critical applications. We really can't afford to push the limits after a few red flags.

Re:Docker in Production: A retort by jwatte on Saturday November 05, 2016 @05:28PM (#12881987)
I have used Erlang and containers, but not in combination. I know that Erlang (really, beam) has some ideas about what the network should behave like, and highly virtualized/"software defined " networking may confuse it.
Re:Docker in Production: A retort by justincormack on Saturday November 05, 2016 @05:04PM (#12881885)
What issues are you having? Containers are not really different from non containerised environments. Have you filed an issue?
Re:Docker in Production: A retort by pmarreck on Saturday November 05, 2016 @11:27PM (#12883342)
It's something I read in another HN thread
Re:Docker in Production: A retort by lobster_johnson on Sunday November 06, 2016 @01:10AM (#12883803)
It runs fine. However, the challenges are the same as any other environment (e.g. AWS): Remember to set a Erlang cookie, and make sure the host name is sane/set and resolvable, otherwise you will run into issues with the portmapper (epmd).
Re:Docker in Production: A retort by bitwalker on Sunday November 06, 2016 @04:17AM (#12884249)
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.
Re:Docker in Production: A retort by pmarreck on Sunday November 06, 2016 @07:43AM (#12884839)
Chokes under significant load, perhaps? Do your erl/iex apps receive much traffic?
Re:Docker in Production: A retort by bitwalker on Sunday November 06, 2016 @06:11PM (#12887644)
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 by empath75 on Saturday November 05, 2016 @06:37PM (#12882307)
Why not use an erlang unikernal instead?