How am I expected to pass

--docker-execution

on the cmdline (from the global options: https://www.pantsbuild.org/v2.19/docs/reference-global#docker_execution)

$ pants --docker-execution test ::
Unknown flag --execution on docker scope

On Pants 2.18 😬

Interesting, maybe because

--docker-execution

is defined at global scope:?https://github.com/pantsbuild/pants/blob/285a7eae68879794868ed3d15a09246207b90740/src/python/pants/option/global_options.py#L1987

Right. I think the docker backend and this option are in collision. With no winner

ouch.

Some ideas: 1. Move

--docker-execution

onto the

docker

subsystem. And add an error during option setup to error on these cases. 2. Teach the option lookup logic to fallback to global scope if it does not find the option on a particular scope.

I’m in favour of (1). Not (2) as I don’t think we should allow having these kind of name conflicts.

I think I lean 2, but I'd have to think more

however, (1) has the downside of then requiring the docker backend to use the core environment feature..?

Not sure about (1) - the docker backend is for your docker builds, whereas this is truly a global thing