tag:help.appveyor.com,2012-11-13:/discussions/problems/20518-problem-with-docker-compose-build-on-windows-server-2019AppVeyor: Discussion 2019-02-23T03:00:15Ztag:help.appveyor.com,2012-11-13:Comment/469756852019-02-19T20:19:01Z2019-02-19T20:19:01ZProblem with docker-compose build on Windows Server 2019<div><p>From what I found about this error, it can be related to the resource limits on the VMs. We temporary upgraded you to "Quad" VMs, which will create <code>Standard_D4s_v3</code> Azure VMs (instead of <code>Standard_D2s_v3</code>) for <code>Windows Server 2019</code> image. Can you please try and let us know if this helps?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/469756852019-02-19T21:57:13Z2019-02-19T21:57:26ZProblem with docker-compose build on Windows Server 2019<div><p>Ilya, I'm now getting:</p>
<pre>
<code>Unhandled Exception: OutOfMemoryException.
Service '*****.ui.iotapp' failed to build: The command '/bin/sh -c dotnet publish KyKenKee.UI.IOTApp.csproj -c Release -o /app' returned a non-zero code: 134
Command executed with exception: Service '*****.ui.iotapp' failed to build: The command '/bin/sh -c dotnet publish KyKenKee.UI.IOTApp.csproj -c Release -o /app' returned a non-zero code: 134</code>
</pre></div>mikejolleytag:help.appveyor.com,2012-11-13:Comment/469756852019-02-19T22:44:59Z2019-02-19T22:55:52ZProblem with docker-compose build on Windows Server 2019<div><p>Can you please run the following in the beginning if your build. <code>install</code> or <code>init</code> stages are good candidate:</p>
<pre>
<code>- ps: gcim Win32_OperatingSystem | % { "$([int]($_.TotalVisibleMemorySize/1mb)) Gb" }</code>
</pre>
<p>Just to ensure it shows 16Gb. And what are specs of your local computer which endures this build?</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/469756852019-02-19T23:31:15Z2019-02-19T23:31:15ZProblem with docker-compose build on Windows Server 2019<div><p><a href="https://ci.appveyor.com/project/AdvancedSystemsUnlimited/kykenkee/builds/22499622">https://ci.appveyor.com/project/AdvancedSystemsUnlimited/kykenkee/b...</a></p>
<p>It does show 16Gb but now I'm bombing on docker-compose:</p>
<pre>
<code>docker-compose : Windows named pipe error: The system cannot find the file specified. (code: 2)
At line:1 char:1
+ docker-compose build
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Windows named p...fied. (code: 2):String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
Command executed with exception: Windows named pipe error: The system cannot find the file specified. (code: 2)</code>
</pre></div>mikejolleytag:help.appveyor.com,2012-11-13:Comment/469756852019-02-20T00:34:28Z2019-02-20T00:34:28ZProblem with docker-compose build on Windows Server 2019<div><p>Can you please try one more time now and let us know?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/469756852019-02-20T01:31:36Z2019-02-20T01:32:09ZProblem with docker-compose build on Windows Server 2019<div><p>Ilya,</p>
<p>Back to the memory error now:</p>
<pre>
<code>MSBUILD : error MSB1025: An internal failure occurred while running MSBuild.
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at Microsoft.Build.CommandLine.MSBuildApp.BuildProject(String projectFile, String[] targets, String toolsVersion, Dictionary`2 globalProperties, Dictionary`2 restoreProperties, ILogger[] loggers, LoggerVerbosity verbosity, DistributedLoggerRecord[] distributedLoggerRecords, Int32 cpuCount, Boolean enableNodeReuse, TextWriter preprocessWriter, Boolean detailedSummary, ISet`1 warningsAsErrors, ISet`1 warningsAsMessages, Boolean enableRestore, ProfilerLogger profilerLogger, Boolean enableProfiler)
at Microsoft.Build.CommandLine.MSBuildApp.Execute(String[] commandLine)
Unhandled Exception: OutOfMemoryException.
Service '*****.ui.iotapp' failed to build: The command '/bin/sh -c dotnet publish KyKenKee.UI.IOTApp.csproj -c Release -o /app' returned a non-zero code: 134
Command executed with exception: Service '*****.ui.iotapp' failed to build: The command '/bin/sh -c dotnet publish KyKenKee.UI.IOTApp.csproj -c Release -o /app' returned a non-zero code: 134</code>
</pre>
<p>It's really odd because these aren't large applications. Unless it's keeping the docker images in memory.</p>
<p><a href="https://ci.appveyor.com/project/AdvancedSystemsUnlimited/kykenkee/builds/22501557">https://ci.appveyor.com/project/AdvancedSystemsUnlimited/kykenkee/b...</a></p></div>mikejolleytag:help.appveyor.com,2012-11-13:Comment/469756852019-02-20T03:56:01Z2019-02-20T03:56:01ZProblem with docker-compose build on Windows Server 2019<div><p>What are your dev machine (where it works OK) specs? We can enable beefier VMs for you temporary to ensure it is just a memory size problem.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/469756852019-02-20T15:05:01Z2019-02-20T15:05:01ZProblem with docker-compose build on Windows Server 2019<div><p>48Gb memory on my dev box</p></div>mikejolleytag:help.appveyor.com,2012-11-13:Comment/469756852019-02-20T18:47:56Z2019-02-20T18:48:29ZProblem with docker-compose build on Windows Server 2019<div><p>I set your account to use <code>Standard_D8s_v3</code> VMs which has 32Gb of memory (no 48 at least in <a href="https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sizes-general#dsv3-series-sup1sup">Dsv3 series</a>, which is essential to use with docker). Let us know if this works.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/469756852019-02-20T19:10:33Z2019-02-20T19:10:33ZProblem with docker-compose build on Windows Server 2019<div><p>Still getting out of memory exception. Can't believe it has anything to do with memory since these are such tiny containers.</p>
<p>Both containers combined are only about 250Mb.</p>
<p><a href="https://ci.appveyor.com/project/AdvancedSystemsUnlimited/kykenkee/builds/22523666">https://ci.appveyor.com/project/AdvancedSystemsUnlimited/kykenkee/b...</a></p></div>mikejolleytag:help.appveyor.com,2012-11-13:Comment/469756852019-02-20T19:13:53Z2019-02-20T19:13:53ZProblem with docker-compose build on Windows Server 2019<div><p>OK, I reset it back to standard VM sizes. Do you believe you can help us with a repro?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/469756852019-02-20T19:24:20Z2019-02-20T19:24:20ZProblem with docker-compose build on Windows Server 2019<div><p>I can try. It's difficult based on that error message. Is it possible to rdp into the machine and run the build commands manually to see what exactly is happening?</p></div>mikejolleytag:help.appveyor.com,2012-11-13:Comment/469756852019-02-20T19:53:09Z2019-02-20T19:53:09ZProblem with docker-compose build on Windows Server 2019<div><p>Sure. Please check <a href="https://www.appveyor.com/docs/how-to/rdp-to-build-worker/">https://www.appveyor.com/docs/how-to/rdp-to-build-worker/</a>.</p>
<p>Thanks a lot for cooperation.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/469756852019-02-23T03:00:12Z2019-02-23T03:00:12ZProblem with docker-compose build on Windows Server 2019<div><p>Ilya,</p>
<p>The problem seems to be that I'm trying to create Linux containers on the Windows box. I've gotten the build working on the Ubuntu1804 image. There should be some way to tell the Windows Server to switch to Linux containers but I couldn't find it.</p>
<p>Thanks!<br>
Mike</p></div>mikejolley