Per Bering

Can you paste the output of `docker info` and the powershell script you use to start the build?

Did you delete stuff that you don't need in `(Join-Path $PSScriptRoot "\images")`? If so please try to pull fresh clone and use `-Tags "*:9.1.1*"` instead.

according to you docker info it seems that your Windows version is 1809, so you cannot build 1903. You can use this tag instead: `-Tags "*:9.1.1-ltsc2019", "sitecore-openjdk:*-1809"`

Hmm it sounds like something with the order of things. Can you try to, in same order, one at the time to build this: `-Tags "sitecore-openjdk:8-nanoserver-1809"`" `-Tags "mssql-developer:2017-windowsservercore-ltsc2019"` `-Tags "sitecore-base:9.1.1-windowsservercore-ltsc2019"`...

I simply cannot reproduce this behavior on any machines I have available (Windows 10 1803, 1903, Windows Server 2019)... Only think I can think of is your Docker version, your...

Great! Both good and bad news :) - I will find a machine to test the edge version on and create a issue on the docker repo if it is...

It's not something I heard off before but it is still good improvements to have here also. Is it something that you see on every machine?

just found out that the issue is still present if you first start **stack1** and the do the second `docker run` line from the description. Is seem that compose is...

@ndeloof not possible, when in "Stopping" state af  trying to run `docker compose down` and I open a new terminal and do `docker ps -a` then I see the container...

Please also notice my statement "_If you **remove** the second port in stack2, it also works as expected, strangely enough..._"... I can run multiple compose projects as long as **each**...