Here a simple docker-compose.yml file to get kong community up and running. It is configured to use postgresql that persists data to a local docker volume. All ports are mapped to localhost only and log goes to stdout/stderr. version: ‘3.4’ services: kong-db: image: ‘postgres:10.1’ ports: – 127.0.0.1:5432:5432 environment: POSTGRES_USER: kong POSTGRES_PASSWORD: kong POSTGRES_DB: kong PGDATA:

In my former post i described a way how to create self signed SSL certificates with an own certificate authority. These certificates didn’t work in latest chrome versions so I updated my scripts to create valid certificates for chrome. This time I only create wildcard certificates because creating one for every subdomain was annoying. #!/bin/bash

Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial Docker version 17.06.0-ce, build 02c1d87 openshift-origin-server-v3.6.0-c4dd4cf-linux-64bit I followed the steps under https://docs.openshift.org/latest/getting_started/administrators.html#downloading-the-binary and got the error in the title. To fix this you have to add “–exec-opt native.cgroupdriver=systemd” to ExecStart of docker. The best way to do this is to add a addin file

Simple way to create self-signed SSL certificates. #!/bin/bash # usage: ./create-ca.sh if [ -e ca.key ]; then echo “ca.key already exists” exit 1 fi openssl genrsa -out ca.key 4096 openssl req -new -x509 -days 3650 -key ca.key -out ca.crt \ -subj “/C=AT/ST=Vienna/L=Vienna/O=coffeebeans.at/OU=IT/CN=coffeebeans.at/emailAddress=office@coffeebeans.at” #!/bin/bash # usage: ./create-key.sh CN NAME=$1 SERIAL=`ls -l *.key | wc -l` if

sudo mkdir /etc/systemd/system/docker.service.d cat /etc/systemd/system/docker.service.d/http-proxy.conf [Service] Environment=”HTTP_PROXY=http://proxy-address:8080/” Environment=”HTTPS_PROXY=http://proxy-address:8080/” Environment=”NO_PROXY=localhost,127.0.0.1,.localdomain” sudo systemctl daemon-reload sudo systemctl restart docker