The Shippable Blog

Deploying Containers to Elastic Beanstalk, the Shippable way!  





We have significantly updated the Shippable platform with several new features. Hence most of the content in this blog is deprecated. For the latest information, refer to our documentation and/or open a support issue, if you have questions.

You can also refer to our new blog on this topic: How To: Deploy your application to AWS Elastic Beanstalk (Part 1)



Last month we introduced the ability to deploy Docker containers to Amazon AWS Elastic Beanstalk (EBS) as the last step in a Shippable CI/CD pipeline.  In this article, I will walk through the steps required to set this up in Shippable and execute a deployment to EBS.

AWS Elastic Beanstalk is an easy-to-use service for deploying and scaling web applications and services developed with Java, .NET, PHP, Node.js, Python, Ruby, Go, and Docker on familiar servers such as Apache, Nginx, Passenger, and IIS.

End-to-end CI/CD pipelines for Docker Hub 2.0


We have significantly updated the Shippable platform with several new features. We fully support CI/CD pipelines for Docker Hub 2.0. Here are few related topics in our documentation.

- Configuring Docker Hub integration for CI/CD

- Tutorial with different scenarios using Docker Hub

Please let us know if you have questions.

Try Shippable

Here at Shippable, we're incredibly excited about the launch of Docker Hub 2.0!  It's no secret that Shippable is a big believer in Docker. Behind the scenes, we've been running Shippable on Docker containers for more than two years now, currently running more than one million Docker containers per week in production.

What may be news, though, is how easily Shippable enables you to incorporate Docker Hub into your software delivery pipeline. And with Docker Hub 2.0, our customers see faster push and pull performance, reducing the cycle time on CI/CD build times and Formations deployment times.

 For an in-depth description and tutorial, check out the white paper "Building a Cloud-based CI/CD Pipeline with Docker, Shippable & GitHub":

Kubernetes Cluster with Flannel Overlay Network


This is the third and final post in the series where we play around with Docker, Kubernetes and Flannel overlay network. The first two posts are available at:
Multi node kubernetes cluster
Docker overlay network using flannel

In this tutorial I’ll explain how to bring up a multi-node kubernetes cluster with an overlay network. This essentially combines what I’ve explained in previous posts. An overlay is necessary to fulfill the networking requirements for a fully functional kubernetes cluster. All this is taken care of auto-magically when the cluster is brought up on GCE, but the manual configuration is slightly complicated -- both because it is non-trivial to set up so many components correctly and with so many tools available for the same job, it is difficult to figure out which one to pick. I picked flannel because of its simplicity and community backing.

Docker image creation, tagging and traceability in Shippable

By now, you've almost surely heard about Docker. Here at Shippable, we've been using Docker and containers for almost two years now and the benefits to how we manage our software delivery and deployment process are impressive. So impressive, in fact, that we're convinced it will revolutionize how all companies do it, making the current DevOps practices obsolete faster than many predict. 

Ultimately, the goal is to deliver value that's derived from software into customers' hands as soon as possible. With Docker images, many of the challenges faced within traditional DevOps approaches are overcome as the creation and deployment of immutable images becomes the new way to deliver software.

The latest features from Shippable make this within reach for any software delivery team as we make it easy for you to create Docker images, push them to your registry of choice, then deploy them without the use of separate DevOps tools or code.  

However, in order to effectively take advantage of immutable Docker images and avoid image chaos, you must have an effective strategy for managing your images. With Shippable, you do this within your CI/CD process flow by automatically creating and tagging your images, with full traceability from final image back to all of the elements used to create it.

The great DevOps 2.0 debate of 2015


Welcome to the great DevOps 2.0 debate! The topic under discussion is - Why is Shippable calling themselves a DevOps 2.0 platform? 

We love Twitterstorms as much as the next person. After all, who can forget the epic exchange between John Legere and The Donald? Or closer to home, the banter between Docker's @shykes and the Coreos folks? Everyone loves a good old-fashioned flame war.

Our announcement on Wednesday ruffled some feathers, albeit important ones. We said that our new product line, Shippable Formations, delivers what we are coining as a DevOps 2.0 platform. And then all hell broke loose. Even Patrick Deboisthe Father of DevOps, was confused and skeptical - 

Patrick's tweet about our DevOps 2.0 announcement 

There was a lot of this going around.