Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Thu, Jun 16, 2016 at 8:47 PM, Nick Coghlan wrote: > On 16 June 2016 at 05:01, Jim Fulton wrote: >> I'm a fan of docker, but it seems to me that build workflow is a an >> unsolved problem if you need build tools that you don't want be >> included at run

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On 16 June 2016 at 05:01, Jim Fulton wrote: > I'm a fan of docker, but it seems to me that build workflow is a an > unsolved problem if you need build tools that you don't want be > included at run time. For OpenShift's source-to-image (which combines builder images with a

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 5:39 PM, Reinout van Rees wrote: > Op 15-06-16 om 13:53 schreef Jim Fulton: >> >> >> 1. Creating production docker images works best when all you're doing >> is installing a bunch of binary artifacts (e.g. .debs, eggs, wheels). > > > That's where pip

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Thu, Jun 16, 2016 at 3:29 AM, Donald Stufft wrote: > Now you install a new version of setuptools that breaks the OS installed > gyp and suddenly now you can’t build your static files anymore. ​gyp or node-gyp don't depend on python-setuptools, at least not on Ubuntu. Are

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 5:10 PM, Ionel Cristian Mărieș wrote: > > On Thu, Jun 16, 2016 at 2:57 AM, Donald Stufft wrote: >> >> Of course It still applies to Docker. You still have an operating system >> inside that container and unless you install zero

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

> On Jun 15, 2016, at 8:10 PM, Ionel Cristian Mărieș wrote: > > ​You're correct, theoretically. But in reality is best to not stick a dozen > services or apps in a single docker image. It’s not really about services as it is about things that you might need *for the

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Thu, Jun 16, 2016 at 2:57 AM, Donald Stufft wrote: > Of course It still applies to Docker. You still have an operating system > inside that container and unless you install zero Python using packages > from the system then all of that can still conflict with your own >

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

> On Jun 15, 2016, at 7:54 PM, Ionel Cristian Mărieș via Distutils-SIG > wrote: > > A sound argument. However, none of that applies to a Docker image. You'd have > a single set of dependencies, so what's the point of using unnecessary tools > and abstractions. :-)​

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Thu, Jun 16, 2016 at 1:52 AM, Reinout van Rees wrote: > Aaargh, that Gliph talk gave me a *lot* of food for thought. And that's a > good thing. > ​His main argument is that not using a virtualenv can lead to version conflicts. Eg: app you installed with apt will probably

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 3:52 PM, Reinout van Rees wrote: [...] > 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

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

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

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

Op 15-06-16 om 13:53 schreef Jim Fulton: 1. Creating production docker images works best when all you're doing is installing a bunch of binary artifacts (e.g. .debs, eggs, wheels). That's where pip and its "everything is in requirements.txt anyway" has an advantage. The buildouts I use

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

Op 15-06-16 om 11:31 schreef Ionel Cristian Mărieș via Distutils-SIG: ... I wrote some ideas about that here if you have patience (it's a bit too long read). I definitively have the patience for such a long

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 2:07 AM, Reinout van Rees wrote: > Situation: I'm experimenting with docker, mostly in combination with > buildout. But it also applies to pip/virtualenv. > ... > Now local development: it is normal to mount the current directory as > /code/, so that

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

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 One point that's discussed is why you definitely should use virtualenv inside your containers :-) -n On Jun 15, 2016 2:07 AM, "Reinout van Rees"

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 7:57 AM, Donald Stufft wrote: > >> On Jun 15, 2016, at 7:53 AM, Jim Fulton wrote: >> >> If you actually build programs as part of image building, then your >> image contains build tools, leading to image bloat and potentially >>

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

> On Jun 15, 2016, at 7:53 AM, Jim Fulton wrote: > > If you actually build programs as part of image building, then your > image contains build tools, leading to image bloat and potentially > security problems as the development tools provide a greater attack > surface.

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 5:07 AM, Reinout van Rees wrote: > Hi, > > Buzzword bingo in the subject... > > Situation: I'm experimenting with docker, mostly in combination with > buildout. But it also applies to pip/virtualenv. > > I build a docker container with a Dockerfile:

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 12:07 PM, Reinout van Rees wrote: > Now local development: it is normal to mount the current directory as > /code/, so that now is overlayed over the originally-added-to-the-docker > /code/. > > This means that anything done inside /code/ is

[Distutils] Docker, development, buildout, virtualenv, local/global install

Hi, Buzzword bingo in the subject... Situation: I'm experimenting with docker, mostly in combination with buildout. But it also applies to pip/virtualenv. I build a docker container with a Dockerfile: install some .deb packages, add the current directory as /code/, run buildout (or pip),