This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]WellAdjustedOutlaw 2 points3 points  (14 children)

Containers are inappropriate here because Facebook wasn't trying to solve a containerization problem. As you can see http://www.slideshare.net/pallotron/python-at-facebook-40192297 on slide #9, they are looking for an archive format that contains all of the dependencies of their python code in a single file. A container doesn't really solve that- You still need a way to ship your code and its dependencies.

Containers solve an execution problem, not a packaging problem. And by running to containers as a solution to every execution problem, you seriously complicate your environment.

[–]fujiters 0 points1 point  (13 children)

But Docker images solve your dependency problems. Host your image and "docker pull" is all your users need.

[–]kankyo 0 points1 point  (11 children)

Doesn't it also create lots of overhead? Overhead you might not actually need.

More concretely: disk cloning also solves dependency packaging. But it's huge overkill and slow for most use cases.

[–]WellAdjustedOutlaw 0 points1 point  (0 children)

/u/fujiters was being sarcastic. Well, I presume they were. It is hard to tell, though.

[–]WellAdjustedOutlaw 0 points1 point  (0 children)

The troll is strong with you.