Skip to main content

Review: Docker Beginners Hands on Full Day Workshop

Hands-on workshops have become a mainstay of Norfolk Developers over the last 18 months. As is well documented they started with a Neo4j workshop following an evening presentation when it became apparent that forty-five minutes just wasn’t enough for some topics. Covering many aspects of software engineering, from databases to JavaScript, the workshops are an opportunity to learn by doing rather than just listening and are created and given by both visiting speakers and our exceptional local talent.

Today it was the turn of Dom Davis of local Techstars Rainbird to tell us about Docker, an open platform for developers and sysadmins of distributed applications. Docker is a hot topic at the moment and a very popular method of deploying applications.

As with a lot of new technologies I’m keen to learn, but struggle to find the time, so a workshop like this one where I have to put the time aside is extremely valuable to me.

A lot of work clearly went into the preparation of the workshop. Each of the twenty one people who took part had three Amazon Web Services (AWS) instances running CoreOS, a version of Debian with Docker pre-installed. One instance for the docker repository, another for development, which got around the cross-platform issues as the participants had the usual mix of Macs, Linux and Windows machines, and one for production to simulate real deployments. Dom has a lot of AWS experience and was able to easily replicate the instances, but he’d also prepared individual small pieces of paper for everyone with the details of their three instances.

Once a few teething problems with Windows users who were relying on Putty to connect to their instances were quickly overcome, we were off! Dom had prepared nineteen exercises each with detailed steps and highlighted gotchas that could be completed via SSH to, in many cases, all three of the allocated instances. The first exercise was actually part of the Docker website where we could use an embedded shell to create Docker images, deploy and interact with them.

The rest of the exercises took us from creating slightly more complex images with Docker files to creating a repository and pushing Docker images to it from the development instance and retrieving and starting them on the production instance. The final few exercises showed us how to create a Node.js Docker image which served a simple message and simulated blue green deployment with a human router.


Throughout the workshop Dom was informative, funny and patient and easily held the attention of the group. Everyone learnt a huge amount about Docker and we’re hoping that as our experience grows and Docker matures, that Dom will come back to give us an intermediate and advanced workshop in the future.



Comments

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv

Bloodstock 2009

This year was one of the best Bloodstock s ever, which surprised me as the line up didn't look too strong. I haven't come away with a list of bands I want to buy all the albums of, but I did enjoy a lot of the performances. Insomnium[6] sound a lot like Swallow the Sun and Paradise Lost. They put on a very good show. I find a lot of old thrash bands quite boring, but Sodom[5] were quite good. They could have done with a second guitarist and the bass broke in the first song and it seemed to take ages to get it fixed. Saxon[8] gave us some some classic traditional heavy metal. Solid, as expected. The best bit was, following the guitarist standing on a monitor, Biff Bifford ripped off the sign saying "DO NOT STAND" and showed it to the audience. Once their sound was sorted, Arch Enemy[10] stole the show. They turned out not only to be the best band of the day, but of the festival, but then that's what you'd expect from Arch Enemy. Carcass[4] were very disappoin

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th