Dockertools: docker-compose ignores DockerfileFastModeStage attribute

[FWest98]

Currently, when using docker-compose support in VS, the generated docker-compose.vs.debug.g.yml file simply takes the first target from the Dockerfile when in fast mode. This ignores the possible custom value you can set in the MSBuild property DockerfileFastModeStage. It would be nice if this attribute would be incorporated in the docker-compose part as well.

Current work-around is to define the target property in a docker-compose.vs.debug.yml file.

[dbreshears]

Thanks for the feedback. Seems like a reasonable request. This is one of those items where the compose tooling was created before the single Dockerfile experience and is the documented approach.

We likely can't get to this right away but will keep it open for investigation to see if we can also honor this MSBuild property from compose, but still have docker-compose-vs.debug.yml override if specified there as well.

[D3MaxT]

Definitely +1 to this request.
Just ran into this today and wasted like 2 hours researching why my multistage dockerfiles weren't working with Compose in debug mode.

Ugh. Please add some priority to this.

[NickMaev]

Any news?

[dbreshears]

It's on our backlog, bumped the priority.

[dbreshears]

@NickMaev . Thanks again for the feedback. When digging into this we unfortunately realized this is a much larger work item than we anticipated in our compose tooling, and have not been able to prioritize with the other work we have. Given the easy workaround and interest in this, our plan is to add the workaround to our official documentation.