Container42 Stuff I find interesting

Twitter GitHub

Docker Grand Ambassador

In Docker, when you want two containers to be able to discover each other and communicate, you use links... Or at least when you first started you did and and then you gave up because links don't work well right now.

The problem with linking is that links are static. When a container which is being linked to is restarted it very likely has a new IP address. Any container which is linked to this restarted container will also need to be restarted in order to pick up this new IP address. Therefore linked containers can often have a cascading effect of needing to restart many containers in order to update links.

read more

DockerHub in dev-test Workflow

When DockerHub was announced there was a really handy feature added that you may have missed: Webhooks.

With DockerHub you can setup a webhook to call out to an external service once a successful push of a particular image is made (this includes completion of automated builds).

This makes for a nice addition to an existing CI/CD workflow.

read more

libswarm demotime - logging

If you don't know what libswarm is take a gander at Libswarm in a nutshell

Just a quick demo showing off what libswarm can do with logging.

I will be using code from this gist:

Demo time!

read more

Libswarm (in a nutshell)

At Dockercon, Docker announced a new project being worked on called libswarm.

I wanted to clarify what exactly libswarm is, what it does, and what it doesn't do.

read more

Docker Quicktip #5: Backing up Volumes

Data in Docker volumes is generally super important. In fact if you are doing your containers correctly the stuff in the volumes is the only thing you need to worry about backing up as containers shouldn't be storing anything at all.

So how do you access the data in volumes?

read more