Stephen Chen RPing

Mistakes to Avoid: Docker Antipatterns

Whichever route you take to implementing containers, you’ll want to steer clear of common pitfalls that can undermine the efficiency of your Docker stack.

Don’t run too many processes inside a single container

The beauty of containers—and an advantage of containers over virtual machines—is that it is easy to make multiple containers interact with one another in order to compose a complete application. There is no need to run a full application inside a single container. Instead, break your application down as much as possible into discrete services, and distribute services across multiple containers. This maximizes flexibility and reliability.

Don’t install operating systems inside Docker containers

It is possible to install a complete Linux operating system inside a container. In most cases, however, this is not necessary. If your goal is to host just a single application or part of an application in the container, you need to install only the essential

MicroService Proxy Gateway Solutions

Kong, Traefik, Caddy, Linkerd, Fabio, Vulcand, and Netflix Zuul seem to be the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to separate the popularity from other things.

Github Star Trend:

This is just a picture of this link from March 2, 2019

Originally, I had included some other solution

Kubectl output options

Let's look at some basic kubectl output options.

Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).

We can start with:

kubectl get no

	#!/bin/bash
	set -e
	set -o pipefail

	# Add user to k8s using service account, no RBAC (must create RBAC after this script)
	if [[ -z "$1" ]] \|\| [[ -z "$2" ]]; then
	echo "usage: $0 <service_account_name> <namespace>"
	exit 1
	fi

	package main

	import (
	"crypto/rand"
	"encoding/base64"
	"fmt"
	"io"
	"math/big"
	)

-#!/usr/bin/env node
-// Channel ID is on the the browser URL.: https://mycompany.slack.com/messages/MYCHANNELID/
-// Pass it as a parameter: node ./delete-slack-messages.js CHANNEL_ID
-// CONFIGURATION #######################################################################################################
-const token = 'SLACK TOKEN';
-// Legacy tokens are no more supported.
-// Please create an app or use an existing Slack App

	#!/bin/bash

	# Copyright © 2017 Google Inc.
	# Licensed under the Apache License, Version 2.0 (the "License");
	# you may not use this file except in compliance with the License.
	# You may obtain a copy of the License at
	#
	# http://www.apache.org/licenses/LICENSE-2.0
	#
	# Unless required by applicable law or agreed to in writing, software

	import asyncio
	from concurrent import futures
	import functools
	import inspect
	import threading

	from grpc import _server

	def _loop_mgr(loop: asyncio.AbstractEventLoop):

	axios({
	url: 'http://localhost:5000/static/example.pdf',
	method: 'GET',
	responseType: 'blob', // important
	}).then((response) => {
	const url = window.URL.createObjectURL(new Blob([response.data]));
	const link = document.createElement('a');
	link.href = url;
	link.setAttribute('download', 'file.pdf');
	document.body.appendChild(link);

	# The initial version
	if [ ! -f .env ]
	then
	export $(cat .env \| xargs)
	fi

	# My favorite from the comments. Thanks @richarddewit & others!
	set -a && source .env && set +a