A couple days ago, someone asked me why they should care about nested containers. It’s a good question, so I thought I’d talk about how I’m using them.
Perhaps my favourite benefit of containers is keeping workloads isolated, and not just in terms of process space. It’s also a great way to avoid dependency bit rot and version conflicts. I have containers for my home media server, for jenkins, for various database servers that I need for this project or that.
bzrsource code control system where running a commit throws an ugly stack trace blaming an “insecure string pickle”, but I’ve found a workaround.
I’ve grown frustrated with Wordpress and Dreamhost. Running a Wordpress site on a shared web host is a ticking time bomb. More users crowded on a server. I threw turned on caching and Cloudflare; readers should have had little trouble using the site, but my sessions were consistently timing out while using the admin dashboard, which makes posting new content a frustrating experience.
sshuttle is a nifty little transparent proxy/vpn that works by tunneling TCP traffic over SSH, or more specifically, tearing down a TCP session and reassembling the data on the other side. I started using it earlier this year, as part of my workflow using Juju and developing under OS X. It’s like a data center in a box, inside another box. Code locally in my editor of choice (vim, TextMate, and more recently, Atom). Deploy new code. Refresh web browser, thanks to sshuttle. With sshuttle, I could connect to the services running within my virtual machine running Ubuntu natively through OS X.