<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker on Chris Ramsay</title><link>https://chrisramsay.co.uk/tag/docker/</link><description>Recent content in Docker on Chris Ramsay</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><copyright>© Chris Ramsay. Content CC BY-NC-SA 4.0 unless stated otherwise.</copyright><lastBuildDate>Sun, 12 Jan 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://chrisramsay.co.uk/tag/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>Pelican Blog Publishing Process Revisited</title><link>https://chrisramsay.co.uk/posts/2020/01/pelican-blog-publishing-process-revisited/</link><pubDate>Sun, 12 Jan 2020 00:00:00 +0000</pubDate><guid>https://chrisramsay.co.uk/posts/2020/01/pelican-blog-publishing-process-revisited/</guid><description>Regarding computer hardware I have had to hand in the last two years or so, things have been in flux, you might say. I have not had ready access to a proper non-work Linux desktop environment where I could happily run Docker and Python. This has meant that keeping my Pelican blog up to date…</description></item><item><title>Pelican Blogging with a Docker Container</title><link>https://chrisramsay.co.uk/posts/2015/12/pelican-blogging-with-a-docker-container/</link><pubDate>Wed, 02 Dec 2015 00:00:00 +0000</pubDate><guid>https://chrisramsay.co.uk/posts/2015/12/pelican-blogging-with-a-docker-container/</guid><description>It has been about a year since I started using a virtual server on the laptop to locally host my blogging efforts with Pelican. Up to now I have used a combination of Vagrant (with Virtualbox in the background) and a Puppet built CentOS VM. At work we are increasingly introducing the concept of containerised…</description></item></channel></rss>