[Preview] Feedback requested on enhancements to compose launch in 17.13 Preview 1

[NCarlsonMSFT]

We've made some big changes in how the .dcproj launches compose services in 17.13 Preview 1 and we need your help to validate that the new experience is meeting your needs!

depends_on

We've added a new way of launching compose (triggered by setting the msbuild property DependencyAwareStart to true) that allows for debugging when declaring dependencies between services.

Turning it on

  <PropertyGroup>
    <DependencyAwareStart>true</DependencyAwareStart>
  </PropertyGroup>

What works

	service_started	service_healthy	service_completed_successfully
linux	✔️	✔️	.NET 6+ (not AOT compiled)
windows	✔️	✔️	❌

replicas / scale

No opt-in needed, this should just work now!

What works

  backend:
    image: ${DOCKER_REGISTRY-}backend
    scale: 2

--or--

  backend:
    image: ${DOCKER_REGISTRY-}backend
    deploy:
      replicas: 2

[jiangyi1985]

this works for me

deploy:
      replicas: 2

but this doesn't

scale: 2

Visual Studio 17.13.0 Preview 2.1
Docker Desktop v4.26.1

[NCarlsonMSFT]

Ivan Jiang (@jiangyi1985) can you provide more context on what is not working?
I just tested on 17.13 Preview 2.1 with:

services:
  webapplication2:
    image: ${DOCKER_REGISTRY-}webapplication2
    scale: 2
    build:
      context: .
      dockerfile: WebApplication2/Dockerfile

And got the two instances as expected

[jiangyi1985]

using replica it works

using scale it doesn't

i found this though
https://stackoverflow.com/a/39663304

By the way I'm on
Docker Desktop v4.26.1
Docker version 24.0.7, build afdd53b
Docker Compose version v2.23.3-desktop.2

[dbreshears]

Both work for me. I am on 4.37.1 of Docker Desktop and Compose: v2.31.0-desktop.2

[NCarlsonMSFT]

Ivan Jiang (@jiangyi1985) I am unable to reproduce this.
It seems that your compose file is starting an instance of the service, but for some reason not the 2nd. The is a decision that is up to docker compose and outside the scope of our tools.
The best thing I can think of to diagnose this is to take one of the docker compose commands you see in the output and copy everything till the last -f parameter and then run docker compose <-f arguments> config to see what the final compose file looks like.

[jiangyi1985]

After using docker compose config to check, there's no scale/replica related code in the final result

@jiangyi1985 I am unable to reproduce this. It seems that your compose file is starting an instance of the service, but for some reason not the 2nd. The is a decision that is up to docker compose and outside the scope of our tools. The best thing I can think of to diagnose this is to take one of the docker compose commands you see in the output and copy everything till the last -f parameter and then run docker compose <-f arguments> config to see what the final compose file looks like.

[NCarlsonMSFT]

Ivan Jiang (@jiangyi1985) the next thing to do would be to inspect each file passed in with -f and check if any of them are overwriting or unsetting your scale property.