containers - Any Idiot ...

Finishing off

Having detailed [https://blog.ervine.org/2018/08/freshly-served-containers/] how I am continually building and publishing my container images, the final post in this series will round off detailing the WordPress installation that this blog is being hosted on. Putting it together It would be very simple to dump all

build

Freshly served containers

Up to this point [https://blog.ervine.org/2018/08/building-my-own-images/] I’ve been able to create my own container images and also store their build configuration on a git repository. My next challenge was to automate building these images and making them available to my kubernetes cluster. It is

containers

[Opinion] Did Docker become pretty irrelevant? (and I'm only just noticing)

Somewhat click-baity post title … but bearing in mind my blog doesn’t get any traffic, I don’t suppose that really matters. This is also 100% completely my own opinion based on nothing but my own current thoughts. That means that in about a year or so I can look

build

Building my own images

I’d finished my previous post [https://blog.ervine.org/2018/08/hello-world-2/] by having setup a gogs git repository instance on my k8s cluster and made this instance accessible to both my local network (HTTP) via an external HAProxy instance and to the wider Internet (HTTPS) through my router

containers

Down the rabbit hole

What’s next for the cluster? Having successfully installed a k8s cluster, the obvious question to ask is ‘what’s next?’ or ‘what do I do with this?’. There are plenty of options available here – basically anything that can run on a Raspberry Pi can be containerised and deployed as