Enable Docker Remote API with TLS client verification

Docker's Remote API can be secured via TLS and client certificate verification.
First of all you need a few certificates and keys:

CA certificate
Server certificate
Server key
Client certificate
Client key

Create certificate files

vijayashankar-g / Docker connect to remote server.md

Created February 11, 2020 06:35 — forked from kekru/Docker connect to remote server.md

Connect to another host with your docker client, without modifying your local Docker installation

Run commands on remote Docker host

This is how to connect to another host with your docker client, without modifying your local Docker installation or when you don't have a local Docker installation.

Enable Docker Remote API

First be sure to enable the Docker Remote API on the remote host.

This can easily be done with a container.
For HTTP connection use jarkt/docker-remote-api.

vijayashankar-g / windows-containers-logging.md

Created February 4, 2020 07:20 — forked from jsturtevant/windows-containers-logging.md

Windows Containers Logging

With Windows Containers, as with any application, you will need to consider your logging strategy. In the containers world it is generally accepted to log to STDOUT/STDERR (standard out and standard error). As you scale up your services you will need to aggregate and store these logs for analysis and debugging later on. There exist many back end systems to aggregate logs and help with analysis, in Azure you have Log Analytics and Application Insights.

There are two general strategies for configuring your containers to send logs to a backend logging system containers:

In container logging - Your application is responsible for sending the logs directly to the backend system. This can also be [configured via sidecar].
Host level logging - You application is configured for sending logs to a log collection agent on the system. The logging agent will