Docker dotnet watch run error: Unable to bind to https://localhost:5000 on the IPv6 loopback interface
Just ran into this problem myself. I don't think dotnet watch run
plays nicely with localhost type urls. Try setting your hosting url to https://0.0.0.0:5000
in your container.
In the dockerfile with:
ENTRYPOINT [ "dotnet", "watch", "run", "--no-restore", "--urls", "https://0.0.0.0:5000"]
Or in launchSettings.json like:
{ "profiles": { "[Put your project name here]": { "commandName": "Project", "launchBrowser": true, "environmentVariables": { "ASPNETCORE_ENVIRONMENT": "Development", "DOTNET_USE_POLLING_FILE_WATCHER": "true" }, "applicationUrl": "https://0.0.0.0:5000/" } }}
Now to get it to automatically reload from within the container you have to use the polling file watcher. That's what the second environment variable is for. (This is pretty common, you've got to do this with webpack, angular, etc).
In your case, you need to change the esportsapp.volume
to a directory on your host:
volumes: - ./:/app
That will map the /app volume in your container to the docker-compose directory. The problem you're facing is that the app is built in a volume on your project's default docker-compose network, so when you change a file in the source directory, it's not actually changing in that volume. With this fix, however, you'll run into the problem of the dotnet restore and dotnet watch inside the container changing your host's files. There's a fix for all of that, if you're interested...
My Usual .Net Core App Docker setup
To debug, run: docker-compose -f run.yml up --build
To build a release: docker-compose -f build.yml up --build
Project structure
/ # source control root/build.yml # docker-compose file for building a release/run.yml # docker-compose file for running locally & debugging/project # an application/project/build.Dockerfile # the docker container that will build "project" for release/project/run.Dockerfile # the docker container that will build and run "project" locally for debugging/project/.dockerignore # speeds up container builds by excluding large directories like "packages" or "node_modules"/project/src # where I hide my source codez/project/src/Project.sln/project/src/Project/Project.csproj/project/src/Project/Directory.Build.props # keeps a docker mapped volume from overwriting .dlls on your host/project/src/Project.Data/Project.Data.csproj # typical .Net project structure/web-api # another application...
Directory.Build.props (put this in the same folder as your .csproj, keeps your dotnet watch run
command from messing with the source directory on your host)
<Project> <PropertyGroup> <DefaultItemExcludes>$(DefaultItemExcludes);$(MSBuildProjectDirectory)/obj/**/*</DefaultItemExcludes> <DefaultItemExcludes>$(DefaultItemExcludes);$(MSBuildProjectDirectory)/bin/**/*</DefaultItemExcludes> </PropertyGroup> <PropertyGroup Condition="'$(DOTNET_RUNNING_IN_CONTAINER)' == 'true'"> <BaseIntermediateOutputPath>$(MSBuildProjectDirectory)/obj/container/</BaseIntermediateOutputPath> <BaseOutputPath>$(MSBuildProjectDirectory)/bin/container/</BaseOutputPath> </PropertyGroup> <PropertyGroup Condition="'$(DOTNET_RUNNING_IN_CONTAINER)' != 'true'"> <BaseIntermediateOutputPath>$(MSBuildProjectDirectory)/obj/local/</BaseIntermediateOutputPath> <BaseOutputPath>$(MSBuildProjectDirectory)/bin/local/</BaseOutputPath> </PropertyGroup></Project>
run.yml (docker-compose.yml for debugging)
version: "3.5"services: project: build: context: ./project dockerfile: run.Dockerfile ports: - 5000:80 volumes: - ./project/src/Project:/app
run.Dockerfile (the Dockerfile for debugging)
FROM microsoft/dotnet:2.1-sdk# install the .net core debuggerRUN apt-get updateRUN apt-get -y --no-install-recommends install unzipRUN apt-get -y --no-install-recommends install procpsRUN rm -rf /var/lib/apt/lists/*RUN curl -sSL https://aka.ms/getvsdbgsh | bash /dev/stdin -v latest -l /vsdbgVOLUME /appWORKDIR /appCMD dotnet watch run --urls http://0.0.0.0:80
build.yml (the docker-compose.yml for building release versions)
version: "3.5"services: project: build: context: ./project dockerfile: build.Dockerfile volumes: - ./project:/app
build.Dockerfile (the Dockerfile for building release versions)
FROM microsoft/dotnet:2.1-sdkVOLUME /app# restore as a separate layer to speed up buildsWORKDIR /srcCOPY src/Project/Project.csproj .RUN dotnet restoreCOPY src/Project/ .CMD dotnet publish -c Release -o /app/out/
There's a simple solution, add the following two lines into your docker-compose.yml file, and the error will disappear.
environment: - ASPNETCORE_URLS=https://+;http://+;
Just wanted to share one other issue I ran recently while containerizing a set of projects even if everything is configured correctly. Hope might help someone else.
Very inconspicuous but some of projects had in Program.cs
:
.ConfigureAppConfiguration((hostingContext, config) =>{ config.Sources.Clear(); ...
Which removes all of the sources and ChainedConfigurationSource
specifically that leads to the error above.