Publishing to Repositories series - Part 1 (Docker Hub)

Preface

As mentioned in the last blog about importance of software delivery, let's start with something I figured out tonight.....

DOCKER HUB

I have been borderline obsessed with Docker lately, primarily because of it's elegance and speed.

Good software must be predictable.

I have been using Docker for delivery of stateless components of my applications like API Server and UI etc. As of last week have also started experimenting with delivering Big Data services on Docker  Storm Kafka Zookeeper for starters (more on this later)

So, how to publish to Docker Hub?

So you have an understanding of Docker, Container and even wrote your own Dockerfile to bake an image and now you are wondering how do I share this with the rest of the community.

In summary, here's what we are going to do:

1. Publish Dockerfile in a github project
2. Signup on Docker Hub
3. Connect Github to Docker Hub
4. Create an Automated build for the project
5. Done

Well here's how you do it:

1. Create an account on Docker Hub at https://hub.docker.com
2. Once you sign-up make you will be sent a verification email, make sure you verify your account. Done?
3. Now you need to make sure your code is published to either Github or Bitbucket (I have only tested with public repositories)
4. If not published create a project on https://github.com and push your Docker project, you need to make sure at the top level of the project is the Dockerfile, if you have other content that's completely reasonable since the Docker build on hub will pull in everything.
5. Next, it's time to login to https://hub.docker.com
6. On the top right side you will see a "Create" drop down, like the one shown below:
7. Click Create Automated Build, you should see:
   
8. Click on the Github icon, your account is not already connected you will be asked to grant permissions to your github repositories so Docker Hub can create web hooks for automated builds.
9. Make sure you grant more privileged access which is required for automated builds.
10. Select the project we created above
11. Now configure the build (default setting are good for first cut, you can always edit them later)
    
    And that's it, Docker Hub will kick off your build! You don't have to worry about massive images being built locally and then copied to Docker Hub; let it do the work and as long as it's the image is public it's all free.
    
    
    Next time, publishing to Maven Central with / without Travis CI.