Boot2Docker is basically legacy - it was the standard way to get going on Windows and Mac before the 'Docker for' options came out without the need for VirtualBox. Docker Toolbox is basically a kit for managing a remote Docker system - not exactly, but that's how I view it. It comes with the client, Docker Machine (for provisioning), and Compose. Given that it's a 'kit' but not a complete enough kit I've been ignoring it.
Jul 10, 2017 Dive Into Docker is a complete course that's packed with examples and best practices. It was carefully crafted to take you from 'What is Docker?' To happily Dockerizing your own applications with.
I'd install Docker for Mac, Docker Compose, and optionally Docker Machine if it fits your need. I have had some horrible performance problem with 'Docker for Mac'. Disk space utilization went through the roof 70GB for just 5 containers. One each of NGinx, RubyOnRails with Puma, PosgreSQL, Redis and Sidekiq and total data.
I've done a bit of googling and while other threads have been started with similar errors they don't match mine and none of the solutions suggested have resolved my issue. I am running Windows 7 (yes I know.) so I am using the docker toolbox. I start up the docker quickstart terminal and then load VS 2017 from the command line.
Visual studio loads and all seems good but when I try to run the docker debugger the debugger stops and I get the following output: - You may only use the Microsoft.NET Core Debugger (vsdbg) with Visual Studio Code, Visual Studio or Visual Studio for Mac software to help you develop and test your applications. Did you mean to run dotnet SDK commands? Please install dotnet SDK from: The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use.NET Core.
![Mac Mac](/uploads/1/2/5/5/125511410/553806163.jpg)
This may be expected if the target process did not run on.NET Core. The program '24 dotnet' has exited with code 145 (0x91). The program ' has exited with code 145 (0x91). I'm not really sure what other information to provide. Here's the docker file (which was generated by the project template) FROM microsoft/aspnetcore:2.0 AS base WORKDIR /app EXPOSE 80 FROM microsoft/aspnetcore-build:2.0 AS build WORKDIR /src COPY WebApi.Core.Basic.UI/WebApi.Core.Basic.UI.csproj WebApi.Core.Basic.UI/ RUN dotnet restore WebApi.Core.Basic.UI/WebApi.Core.Basic.UI.csproj COPY. WORKDIR /src/WebApi.Core.Basic.UI RUN dotnet build WebApi.Core.Basic.UI.csproj -c Release -o /app FROM build AS publish RUN dotnet publish WebApi.Core.Basic.UI.csproj -c Release -o /app FROM base AS final WORKDIR /app COPY -from=publish /app.
ENTRYPOINT 'dotnet', 'WebApi.Core.Basic.UI.dll' Let me know if there are other details which would help me resolve the issue. I'm a bit of a.nix noob but my first thought is if I knew the exact command visual studio is running behind the scenes in docker I might be able to see some additional information? How might I find that command?
Does that command produce a log? Where is that log located? I downloaded the binaries thinking I could manually place them in the dotnet/shared folder but the folder structures don't match so I'd just be guessing. Decided to try to see if 2.1 would work.
Set the project to target.Net Core 2.1 and updated the docker file per the readme here: FROM microsoft/dotnet:2.1-aspnetcore-runtime AS base WORKDIR /app EXPOSE 80 FROM microsoft/dotnet:2.1-sdk AS build WORKDIR /src COPY WebApi.Core.Basic.UI/WebApi.Core.Basic.UI.csproj WebApi.Core.Basic.UI/ RUN dotnet restore WebApi.Core.Basic.UI/WebApi.Core.Basic.UI.csproj COPY. WORKDIR /src/WebApi.Core.Basic.UI RUN dotnet build WebApi.Core.Basic.UI.csproj -c Release -o /app FROM build AS publish RUN dotnet publish WebApi.Core.Basic.UI.csproj -c Release -o /app FROM base AS final WORKDIR /app COPY -from=publish /app. ENTRYPOINT 'dotnet', 'WebApi.Core.Basic.UI.dll' Unfortunately I got the same error.:( It occurs to me that since the project is building I can try to get docker to run it using the command line to see if that tells me anything.