#13682 Add support for cross-building Python applications to `test`, `package` inside-of/for a Docker image Issue created by ryanking Is your feature request related to a problem? Please describe. My problem is that we have a good chunk of python code which depends on a lot of system libraries and command line tools being on the PATH. This is bioinformatics code for which this pattern is quite common. This code will run in a container, whose image is built by pants, in CI and production. When running tests in development environments I would like to be able to use the same environment. Describe the solution you'd like I would like to be able to tell pants– "when running this target, run it in a container from _this image_". Ideally that image can be built by pants automatically when needed. Describe alternatives you've considered One alternative we are considering is to move all our development work to linux machines and/or docker containers where we have everything installed. (We may do this regardless of this change). Additional context slack discussion - https://pantsbuild.slack.com/archives/C046T6T9U/p1637272879490300 * * * Notes from #14145: Cross-building Python dists (wheels) to target a different platform could be accomplished internally to Pants using Docker, to allow both cross-platform PEXes and Docker images to be built without pre-built dists. Cross-building inside of a docker image is very similar to remote execution to a different plaform (as described in #11148): at a fundamental level, it's a bit like executing all logic remotely inside of the container. Similarly, it involves isolating the subgraph in which the cross-build is occuring using a different `Platform`/`Environment`. pantsbuild/pants

#13682 Add support for cross-building Python applications to `test`, `package` inside-of/for a Docker image Issue closed as completed by stuhood pantsbuild/pants