I had a python+docker case I'm tying to prototype with pants and ran into a "glibc on the workstation being newer than the docker image --> bad wheels" style of problem. I took the new environments feature for a spin. It transparently(!!?) built the wheels/pex/etc in the same base builder image we use in CI. That was pretty sweet! I was trying to

pants run

the app though and ran into some overlapping problems. • (A) If I `pants run src/py/foo:the-docker-target", then AFAIK there isn't any way to pass along docker options (in the sense of

docker run [OPTIONS] IMAGE [COMMAND] [ARG...]

). The app takes it's configuration from environmental variables that it needs at run (not build) time. • (B) With

pants run src/py/foo:the-pex-target

I get "The

run

goal only runs in the local environment. You may experience unexpected behavior.", which I presume is a pending feature and not a fundamental limitation. • (C) Just invoke

docker run

directly. That works, but the target is a little webapp and this would leave no path towards

restartable=True

or better workflows <https://github.com/pantsbuild/pants/issues/17414>