To view the details of this network, just type the powershell command –

get-containernetwork

To view the network at the host level, type ipconfig – it should show up as a virtual network that is different from the actual physical ethernet network.

To see what new types of networks can be created, type

new-containernetwork

To update the docker daemon.json file

1. invoke item (ii) from a powershell prompt – and browse to c:\program files\docker\

2. Edit the range of private IP addresses, if that’s what you want for your default NAT network.

3. Edit to bridge = none – to use a Transparent network (instead of the default NAT network)

The post ipconfig–virtual ethernets and real ethernets, docker networking daemon appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

If docker engine (daemon) does not start up

 — Install-Package -Name docker -ProviderName DockerMsftProvider -verbose (from an admin PS prompt)

To completely remove docker desktop from your Windows 10/ Windows Server installation

$ErrorActionPreference = “SilentlyContinue”
Stop-Process -force -processname ‘Docker for Windows’, com.docker.db, vpnkit, com.docker.proxy, com.docker.9pdb, moby-diag-dl, dockerd
try {
 ./MobyLinux.ps1 -Destroy
 } Catch {}
$service = Get-WmiObject -Class Win32_Service -Filter “Name=’com.docker.service’”
 if ($service) { $service.StopService() }
 if ($service) { $service.Delete() }
 Start-Sleep -s 5
 Remove-Item -Recurse -Force “~/AppData/Local/Docker”
 Remove-Item -Recurse -Force “~/AppData/Roaming/Docker”
 if (Test-Path “C:\ProgramData\Docker”) { takeown.exe /F “C:\ProgramData\Docker” /R /A /D Y }
 if (Test-Path “C:\ProgramData\Docker”) { icacls “C:\ProgramData\Docker\” /T /C /grant Administrators:F }
 Remove-Item -Recurse -Force “C:\ProgramData\Docker”
 Remove-Item -Recurse -Force “C:\Program Files\Docker”
 Remove-Item -Recurse -Force “C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Docker”
 Remove-Item -Force “C:\Users\Public\Desktop\Docker for Windows.lnk”
 Get-ChildItem HKLM:\software\microsoft\windows\currentversion\uninstall | % {Get-ItemProperty $_.PSPath} | ? { $_.DisplayName -eq “Docker” } | Remove-Item -Recurse -Force
 Get-ChildItem HKLM:\software\classes\installer\products | % {Get-ItemProperty $_.pspath} | ? { $_.ProductName -eq “Docker” } | Remove-Item -Recurse -Force
 Get-Item ‘HKLM:\software\Docker Inc.’ | Remove-Item -Recurse -Force
 Get-ItemProperty HKCU:\software\microsoft\windows\currentversion\Run -name “Docker for Windows” | Remove-Item -Recurse -Force

If you see this error on docker compose

Docker Network Create Fails: HNS failed with error : The object already exists 

– This comes from a port conflict — if you have 443:443 in more than one place (in two different services)

The post Docker Install Uninstall Issues appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

First, of course, get the ID of the running container

docker container ls -a (show me all the running containers on this host).

docker exec -i -t 1aa86f5bf93a | PS
docker run -it <image-name> powershell docker r

To connect to docker and launch a PS prompt inside the container

docker exec CONTAINERID

To Inspect a folder or a file inside the container

docker exec containeriD | ls <dir path>

To List all the processes inside the container

First connect to it using docker exec and launch a PS prompt

 docker exec <container> | PS

Then, just use Powershell’s

        List-processes

To view the event log inside the container (once you have a PS prompt using     docker exec <container> | PS  )

get-eventlog system -newest 10000 | format-table -wrap > c:\data\syslog.txt (if c:\data is defined as a volume, it can be read from the host)

# this shows source as ‘Docker’ but can change you ‘Application’ or custom

Get-EventLog -LogName Application -Source Docker -After (Get-Date).AddMinutes(-5) | Sort-Object Time

#To search for specific terms in an event log

Get-WinEvent –listlog *mykeyword*

To Copy files from host to container

 docker cp foo.txt mycontainer:/foo.txthttp:

To Inspect all the properties (volumes, ports…) of a running container

First get the ip address of the running container – lookup the container id (docker container ls)

docker inspect c5e8de7faf05 - will give you the IP

docker inspect --format='{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' $INSTANCE_ID

To Automate hitting a container URL

curl -i "https://$(docker-machine ip node-1) (If no curl, use powershell as shown below)
Invoke-WebRequest -Uri https://$(docker-machine ip node-1)  | Select-Object -ExpandProperty Content
Invoke-WebRequest http://localhost -method GET

To push/pull docker images from an external registry (e.g. Azure Container Registry)

$env:docker_registry = “myregistry.azurecr.io“

docker login -u myregistry –p password myregistry.azurecr.io

docker-compose push/pull

Summary

I have been fortunate to work as a docker architect for a few oil and gas companies in Houston, TX – as well as state agencies in Austin, TX. These are just some commands I found helpful while working with and testing containers – in my role as a docker architect. docker exec should be your go to command for getting access to a running container. Once in, you can run powershell just like you would on a windows host. Of course, if you are on linux, you would use bash or some other scripting platform.

Thoughts? Comments?

The post Inspecting Running Containers (Docker Containers) appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

To connect to docker and launch a PS prompt inside the container

docker exec CONTAINERID

To fetch the newest 1000 events in the Application Event log (the format is needed to avoid truncation)

Get-EventLog Application –Newest 1000 | format-table -wrap 

To search for specific terms in an event log

Get-WinEvent –listlog *mykeyword*

The post Event Logs and Running Containers appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

• a) Setup prometheus on the host or inside a container.
• b) Configure your App to post to a prometheus endpoint and
• c) Non Prometheus based commands for inspecting running containers.

Prometheus – Standalone or as a container ?

Prometheus can be run as a  standalone exe on the host OR can run it inside a docker container. The recommendation is to run it inside a container; however, if you are not running a swarm of services, you could just  set it up on the host.

Prometheus on the Host – Setup

1. Download and extract prometheus.exe; add c:\prometheus to your path

https://github.com/prometheus/prometheus/releases/download/v2.7.1/prometheus-2.7.1.windows-amd64.tar.gz

2. Create default YAML file

3. Start it using –

prometheus --config.file "\tmp\prometheus.yml"

4.  Test localhost:9090/graphs

Prometheus as a container – Setup

docker run -p 9090:9090 prom/prometheus

5. https://www.prometheusbook.com/MonitoringWithPrometheus_sample.pdf

Downside of Prometheus based Logging

Prometheus , due to it’s constant calculation engine,  uses between 8 and 10 GB RAM (whether running on the host or in a container).  This may not be a feasible option for several server VMs, which have little extra memory to spare.

To Log App Specific Metrics – Application Specific Setup

To expose the /metrics endpoint from your application, you  need to install prometheus client libraries for your app (as shown in the URL below).

https://coreos.com/operators/prometheus/docs/latest/exposing-metrics.html

Summary

Appendix : Quick Inspection of Containers (without Prometheus) – Inspecting Running Containers and Viewing Event Logs

To connect to docker and launch a PS prompt inside the container

docker exec CONTAINERID

To Inspect a folder or a file inside the container

docker exec containeriD | ls <dir path>

To List all the processes inside the container

    First connect to it using docker exec and launch a PS prompt

 docker exec <container> | PS 

    Then, just use Powershell’s

        List-processes 

To view the event log inside the container (once you have a PS prompt using     docker exec <container> | PS  )

get-eventlog system -newest 10000 | format-table -wrap > c:\data\syslog.txt (if c:\data is defined as a volume, it can be read from the host) 

# this shows source as ‘Docker’ but can change you ‘Application’ or custom

Get-EventLog -LogName Application -Source Docker -After (Get-Date).AddMinutes(-5) | Sort-Object Time 

#To search for specific terms in an event log

Get-WinEvent –listlog *mykeyword*

To Copy files from host to container

 docker cp foo.txt mycontainer:/foo.txthttp:

To Inspect all the properties (volumes, ports…) of a running container

First get the ip address of the running container – lookup the container id (docker container ls)

docker inspect c5e8de7faf05 - will give you the IP

docker inspect --format='{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' $INSTANCE_ID 

The post Docker Application Logging Using Prometheus appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

What do you do if you require more than one command to execute when your container starts up?

The answer is simple – but getting it work was not trivial. The idea is to wrap up those tasks in powershell scripts (say bootstrap.ps1) – and assign the ENTRYPOINT to the bootstrap script.

Why was this a challenge to get working?

The challenge wasn’t with assigning the Powershell script as the startup ENTRYPOINT command. That worked just fine. The challenge was to do that – AND to restart IIS (or whatever webserver/aspnet dll / app entrypoint) – your application’s true entrypoint – at the same time. Again, the fact that you can only assign ONE ENTRYPOINT command, kept me searching for the answer.

It turns out you can concatenate your ENTRYPOINT commands – provided you start with POWERSHELL – and use Powershell concatenation as shown in the last line below.

version: '3.7'

services:

  web:

     env_file: .\variables.env

     build:

     context: .\web

     dockerfile: Dockerfile

      ports:

      - "80"

      - "443:443"

     security_opt:

      - credentialspec=file://mywebsite.json

     hostname: mywebsite

     volumes:

      - c:\Data:c:\Data

      - c:\certs:c:\certs

     entrypoint: cmd /c "powershell \bootstrap.ps1 & C:\\ServiceMonitor.exe w3svc"

Summary

Dockerfile instructions are concise and thus, deceptively simple. There seem to be limitations imposed by docker, but it turns out, with a little powershell, these limitations can be easily overcome. This post describes a way to assign multiple startup , entrypoint commands – something I found, a lot of people struggling with.

The post dockerfile MULTIPLE commands or entrypoints–Powershell and IIS as ENTRYPOINTS in Docker Compose appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.