Op 15-06-16 om 19:38 schreef Nathaniel Smith:
For a lot of good general information on these subjects, I recommend Glyph's talk at pycon this year: https://www.youtube.com/watch?v=5BqAeN-F9Qs
That's the most valuable youtube video I saw this year!
One point that's discussed is why you definitely should use virtualenv inside your containers :-)
Seems like a very valid point.
It is a very valid point that seems to point solidly at wheels. As, if you use a virtualenv, you don't have access to system python packages. And that's one of the main reasons why the company I work for (still) uses buildout. Buildout has the "syseggrecipe" package that makes it easy to use specific system packages. So.... numpy, psycopg2, matplotlib, mapnik, scipy, hard-to-install packages like that.
So once you use a virtualenv, you're either in a hell because you're compiling all those hard-to-compile packages from scratch, or you're using binary wheels.
Once you've chucked everything into a wheel, there's suddenly a bit less of a necessity for docker. At least, that might be the case.
On the other hand, I could imagine having a base 16.04 docker that we build to instead of a manylinux1 machine that we build to.
Aaargh, that Gliph talk gave me a *lot* of food for thought. And that's a good thing.