Make sure you add the docker compose project file (.dcproj) into your solution, then you can run the whole application with one click with debug capabilities.
Setting it up with other development environments is another matter.
Month: March 2022
Docker desktop using all the RAM
Some applications will use as much resources as possible, like Elasticsearch.
If you are running Docker for development and it uses up all your resources because of such application, you can configure the Docker backend to limit the amount of resources it can use.
If your Docker desktop is using WSL2 as backend, create a .wslconfig file in your user home folder in Windows with the following content
[wsl2]
memory=6GB
processors=4
Then, restart the WSL backend in Powershell
Restart-Service LxssManager
This will also restart Docker Desktop.
This will limit the resources Docker will use to only 6GB RAM and 4 core processors, leaving resources for your other applications and development tools.
Cannot restore internal NuGet packages
When working with projects that has dependencies on an internal NuGet registry, you may need add credentials for the internal registry so that NuGet can fetch the packages.
If you restore in Visual Studio, it’s possible that VS will ask you to provide credentials (not yet tested).
If you try to restore or build using the command line, it may fail with unauthorized error.
To resolve, modify nuget.config file, either in the same folder of the solution file, or modify the global nuget.config file.
<packageSourceCredentials>
<MyPrivateNugetRegistry>
<add key=”Username” value=”Your username here” />
<add key=”ClearTextPassword” value=”your password/access token here” />
</MyPrivateNugetRegistry>
</packageSourceCredentials>