Developing with Docker on Windows

-

Installation

First install chocolatey

Then choco install docker-for-windows

Install vscode plugin Docker

Run a Dockerfile from vscode

Open “Docker Desktop” from start menu, and wait for the popup “Docker Desktop is now up and running”

In vscode right click Dockerfile -> Build -> hit enter to give it the default name.

In vscode on the Docker plugin tab, right click the image -> run interactive.

CLI Snippets

Take a look here for some fairly decent snippets.

Build a Docker Image

docker build -t image123 .

Run a Docker Container, and Open a Shell

docker run -it --name container123 image123

Run a Docker Container, Exposed on Port 25000, With An EntryPoint Defined in *.dll, and Delete the Container After Exiting the Shell

docker run -it -d --name container123 -p 25000:80 --entrypoint="dotnet" image123 YourAssemblyWithAnEntryPoint.dll

Inspect a Docker Containers’ File System That is Already Deployed

# list the running docker containers, look for the {containerid} for your container
docker ps -a -q
# create a snapshot, run it and open a shell
docker commit {containerid} mysnapshot
docker run -t -i mysnapshot /bin/bash
# when finished inspecting, delete the snapshot with:
docker rmi mysnapshot

Delete All Docker Images (dev machine only)

docker stop $(docker ps -q)
# a more brutal way of stopped a container than the above
docker kill $(docker ps -q)
docker rmi $(docker images -q)

Inspect the entire docker configuration, including port bindings/forwarding

docker inspect {containername}

Popular posts from this blog

Taking a memory dump of a w3wp process

-
Taking a memory dump of a w3wp process Taking a memory dump of an IIS worker process in a live system can be problematic, as IIS will kill the process if it has been suspended for more than 60 seconds. Only use these steps if your application is on a high availability cluster, else you’ll take your app down! copy sysinternals procdump.exe and pssuspend.exe to target machine create powershell file with: $iispid = Get-Process svchost | ? { $_ . modules . ModuleName -eq "iisw3adm.dll" } | Select - First 1 - ExpandProperty Id $workerpid = Get-Process w3wp | Sort ws - Descending | Select - First 1 - ExpandProperty Id & ".\pssuspend.exe" $iispid Write-Output "Creating memory dump for w3wp PID $workerpid " & ".\procdump.exe" - ma $workerpid & ".\pssuspend.exe" $iispid - r (taken from stackoverflow ) 3) check the w3wp process has reached the high level of RAM usage that you’re intending to
Read more

GitLab Badges

-
Image
GitLab has built in functionality to allow you to add badges, to provide an at-a-glance status of your app's quality.  In order to set project badges up, you need to be a maintainer of the project so that you can access the settings. Pipeline Status This shows whether your master branch pipeline has passed or failed.  The badge is super easy to set up.  In GitLab go to Settings > General > Badges > Add Badge, and enter this: Name:  Pipeline Link:  https://gitlab.com/%{project_path}/commits/%{default_branch} Badge: https://gitlab.com/%{project_path}/badges/%{default_branch}/pipeline.svg These links should be right for any project, as they're using variables. Coverage % Code coverage is a little more involved, as it relies on you having already configured code coverage in your app.  For the app I've been working on, which is a dotnet application, I opted to use the opensource MiniCover .  This is configured to writes a code coverage report to the
Read more

sp_blitzIndex

-
Some more notes after watching Brent’s How I Use the First Responder Kit: sp BlitzIndex . This sproc will analyse every index across all databases in your sql server and return a prioritised list of potential issues. EXEC sp_blitzIndex @GetAllDatabases = 1 The MoreInfo column is interesting. If you copy the SQL out and run it, it will give you more information on the indexing issue in question. E.g: EXEC dbo . sp_BlitzIndex @DatabaseName = 'YourDatabase' , @SchemaName = 'dbo' , @TableName = 'tFoo' ; If you run this, the top result set it a list of indexes that are on the target table. It shows how many seeks and scans each index has had, the size of the index, etc. Note the URL column for more information on each issue category. Missing indexes are shown in the 2nd result set. The 3rd result set shows the table definition, which is nice to have without having to mess with the SSMS UI.
Read more