[erlang-questions] Programming Erlang: Chap 18, Websockets

Rick Pettit rpettit@REDACTED
Tue Jun 27 20:48:49 CEST 2017

Marco, I’m not sure I follow.

Aren’t you forced to expose your Erlang application to a network, thus "opening it up to attack", regardless of whether or not docker or some VM is in the picture?

In what ways does adding Docker make that problem “worse”, in your opinion?


> On Jun 27, 2017, at 1:25 PM, Marco Molteni <marco.molteni@REDACTED> wrote:
> On 27 Jun 2017, at 09:00, <ok@REDACTED> <ok@REDACTED> wrote:
>> As I understand it, this is one of the driving forces behind
>> the application = VM approach using Docker and the like:
>> make a VM containing the things your application needs and
>> as little else as you can manage, and then never change it.
>> If you want a new version of the application, make a new VM.
> This sounds good on the surface (the charm of Docker).
> Then one realises that the container is exposed to a network, and so open to attack.
> Then one understand that the less worse approach is to keep updating everything and fixing what breaks.
> marco
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

More information about the erlang-questions mailing list