I’m trying to understand how the jobs’s python virtualenv may differ from the code location’s python virtualenv. It looks that by default, jobs are spun from the same docker image. Would it be possible to spin up code-locations with different images, or similarly, the same image, but different using different virtualenvs. (This is about specifying differences between jobs and code-location, not configuration for container ops.)

this might be along the lines of what you're looking for with regards to different images. I don't think Dagster does anything specifically with virtualenvs, that seems more dependent on how you build your container

Hi Simon-- a little confused by this part of your question:

understand how the jobs’s python virtualenv may differ from the code location’s python virtualenv… Would it be possible to spin up code-locations with different images, or similarly, the same image, but different using different virtualenvs.

Are you trying to spin up multiple code locations with different virtualenvs, or launch multiple jobs from the same code location but with different virtualenvs?

@sean the latter - I’m trying to use the same code-location for different jobs, each with it’s own virtualenv

OK I’m going to call in a colleague who knows these APIs better.