Sometimes there are problems to export a website certificate that is not trusted by one of the major CAs (self-signed or development certificates for example). Usually you’d open the certificate details in Chrome, then drag and drop the image icon to any folder on your computer (for example your Desktop). Then you’d double click it and import… Continue Reading Export Website Certificate from Chrome on OSX
When creating new docker-machine Docker nodes, one needs to add necessary root CA certificates to them in order to let them communicate with SSL protected services. The easiest, if manual, method is to copy the ca certificate (in .pem format) to /var/lib/boot2docker/certs on EVERY swarm node (if running in swarm mode).
What the shait this has been annoying… Well, here is the bottom line: Issue Your Own Self-Signed S/MIME Certs with OpenSSL by using these two shell scripts: makeauthority.sh makecert.sh
If you have ever been annoyed by ps aux output being truncated, this comes to your rescue:
According to play-with-docker.com you can trust a self-signed cert by doing the following: If you are running the registry locally, be sure to use your host name as the CN.To get the docker daemon to trust the certificate, copy the domain.crt file. Make sure to restart the docker daemon. The /dev/null part is to avoid the output… Continue Reading Reminder: Make Docker trust certificates
I got a RasPi as an early christmas gift and this post is just to remind me later what I did to set it up. Reminder to begin with, if you’re not me: I work with a Mac, so this setup is from an OSX perspective. It might apply to other unix-like Systems but you… Continue Reading Setup for my Raspberry Pi
Gitlab follows semantiv versioning. It even does not allow you to upgrade from a non-latest minor version to a new major version. Meaning: 10.1 -> 11.4 is now allowed if there is a 10.8 version. Thus you need to upgrade in steps: 10.1 -> 10.8 -> 11.4 (for example). Procedure: # Create a backup (Don’t… Continue Reading Upgrading Gitlab
The setting: $ docker network rm myNetwork Error response from daemon: rpc error: code = FailedPrecondition desc = network kny0nsuae9ymnpzjzufrefn9a is in use by task iczzsz7yrrafhn08y1slnhr8l The solution: $ docker pull dperny/tasknuke! $ docker run -v /var/run/docker/swarm/control.sock:/var/run/swarmd.sock dperny/tasknuke iczzsz7yrrafhn08y1slnhr8l iczzsz7yrrafhn08y1slnhr8l The glorious source: success.docker.com – How to force remove an orphaned task from a network
When you’re in a Docker container, ideally you don’t want to have to enter the container in order to read log files. It’d be best to have everything on stdout and stderr of your container so Docker picks them up automatically and thus delivers it to any logging driver you attach. This is thankfully easily… Continue Reading Docker: Symlink your log files to stdout and stderr!
Puh…this is a big one… A client contacted me saying the webserver’s logs on one of our swarm stacks reports the same IP address for any request and it’s not one of any of the clients used: – 10.255.0.2 [18/Oct/2018:13:38:43 +0000] “GET / HTTP/1.0” 401 113 “HTTP-Monitor/1.1” 1 This is an issue as we require… Continue Reading Getting original client IP from a request in Docker Swarm – Or the issue with issue #25526