Specifying "--compatibility" flag with docker-compose project

[GAAOPS]

Hi,
I am developing on windows 10 machine and because Windows 10 supports only "HyperV" isolation and it is limited to 1GB memory by default,i created my docker compose file like this:

version: '3.6'

services:
  website:
    ports:
      - "80"
    volumes:
      - .\storage\Data:C:\inetpub\sc\Data
    deploy:
      resources:
        limits:
          memory: 5GB
        reservations:
          memory: 3GB
    build:
      dockerfile: Dockerfile
      args:
        source: obj/Docker/empty
    
    volumes:
      - .\storage\Website\:C:\inetpub\sc\website
    entrypoint: powershell -Command "C:/DebugBoot.ps1;C:/remote_debugger/x64/msvsmon.exe /noauth /anyuser /silent /nostatus /noclrwarn /nosecuritywarn /nofirewallwarn /nowowwarn /timeout:2147483646;C:/ServiceMonitor.exe w3svc;"

Docker 3.x supports swarm mode and if i want to use mem_limit features from docker compose 2.x then i must pass the --compatibility flag to docker compose (see the discussion here: docker/compose#4513 and docker/compose#5684), this will works for me from command prompt:

docker-compose --compatibility up -d --force-recreate

My base image is :"microsoft/aspnet:4.7.1-windowsservercore-ltsc2016"

I couldn't find a way to pass in the --compatibility in visual studio, is it possible at all?

[haniamr]

It is not possible to pass specific arguments to docker-compose, however you can override the build task with your own (which is tricky and non-trivial), see #46 for an example.

[GAAOPS]

Thanks a lot, I got it to work, as you said it was not a trivial task.
In the end, I have to override the "PrepareForLaunch" Task and DockerComposeClient, DockerWorkspace and the MergedDockerComposeDocumentProvider,... .

I have another question, may I publish the code to GitHub, it would be useful for others.
I don't know how the licensing works, so if you can confirm it is no problem I would like to share it with others.

Thanks again.

[haniamr]

Thanks @STDGA for sharing this, i'm glad it worked! Honestly, I'm not sure I have the answer to that, Devin Breshears (@dbreshears) any thoughts?

[becio]

I need this flag too because I have a container that eats a lot of memory and I want to test how it behaves locally by setting a limit, I can't find an easy way of doing this from VS, there should be an option in the settings to enable this compatibility mode, until that I have to test this from outside VS by switching to swarm mode and using command prompt.

[robece]

@STDGA hey impressive, I'm really interested about see that implementation, I need to customize my docker implementation too, I don't want to install and configure Kubernetes just for a memory limit handling in non-swarm scenarios, do you have any public documentation about that? or can you share with me the changes you performed? thank you.

[pratiksanglikar]

It is possible to pass different arguments to the Docker commands through MSBuild properties.
Check usage of DockerComposeBuildArguments, DockerComposeDownArguments and DockerComposeUpArguments.
https://docs.microsoft.com/en-us/visualstudio/containers/docker-compose-properties

[Gapmeister66]

Sorry, I posted to the wrong project. I have deleted my comment to avoid confusion. Thanks for the reply, pratiksanglikar

[richardgundersen]

Hi Pratik Sanglikar (@pratiksanglikar), is it possible to set the --compatibility flag this way? The closest parameter I can see is DockerComposeUpArguments, but if I put

<DockerComposeBuildArguments>--compatibility</DockerComposeBuildArguments>

into the dcproj file it adds the flag after the 'up' command, whereas the --compatibility flag seems to need to be inserted before.