Skip to main content

Docker Automated Builds

When it comes to "dockerization" of your application, it might be possible that your apps are under continuous development and needs to generate new docker image frequently based on the app updation.
So, if haven't gone through my previous Articles regarding Docker Overview and Docker Basics, then please go through those first.

Solution: Automation of the Docker Build using Docker Automated Build feature of hub.docker.com

How? Let's find out.

All we have to do is to link Docker and Github to automate the build process. Following steps will teach you to do so with a sample project on Github.

Step 1: Create account on both Github.com and hub.docker.com

Step 2: Create a repository on the Github as per your requirements.

Step 3: Create a file named as "Dockerfile" with the following contents


FROM ubuntu:16.04

USER root
WORKDIR /root

RUN apt-get update -y \
    && apt-get install -y apache2

RUN service apache2 restart

EXPOSE 80:8080


Step 4: Commit and merge with the master.

Step 5: Go the hub.docker.com

Open Create > Create Automated build
Click Automated Build with Github

Step 6: Follow the steps to grant full access of Github account to the hub.docker.com

Step 7: Select your Github repository ,fill out the description and click Create.

Step 8: Commit some changes in your Github repository to trigger the Build. (Like changes in README.md file)

Step 9: Come back to hub.docker.com, open your Automated build repository and open the build section. You will find one build running. It will take couple of minutes to finish.

In the end your Docker image will be ready with the latest tag.
Labels:

Comments

Post a Comment

Popular posts from this blog

Ceph Single Node Setup Ubuntu

Single Node Ceph Install A quick guide for installing Ceph on a single node for demo purposes. It almost goes without saying that this is for tire-kickers who just want to test out the software. Ceph is a powerful distributed storage platform with a focus on spreading the failure domain across disks, servers, racks, pods, and datacenters. It doesn’t get a chance to shine if limited to a single node. With that said, let’s get on with it. Inspired from:  http://palmerville.github.io/2016/04/30/single-node-ceph-install.html Hardware This example uses a VMware Workstation 11 VM with 4 disks attached (1 for OS/App, 3 for Storage). Those installing on physical hardware for a more permanent home setup will obviously want to increase the OS disks for redundancy. To get started create a new VM with the following specs: ·         Name: ceph-single-node ·         Type: Linux ·         Version: Ubuntu 16.04.03 (64-bit) ·         Memory: 4GB ·         Disk: 25GB (Dynamic) ·
1 comment
Read more

Docker Overview

OVERVIEW Docker is the company driving the container movement and the only container platform provider to address every application across the hybrid cloud. Today’s businesses are under pressure to digitally transform but are constrained by existing applications and infrastructure while rationalizing an increasingly diverse portfolio of clouds, datacenters and application architectures. Docker enables true independence between applications and infrastructure and developers and IT ops to unlock their potential and creates a model for better collaboration and innovation. A little intro to LXC: - LXC (LinuX Containers) is a OS-level virtualization technology that allows creation and running of multiple isolated Linux virtual environments (VE) on a single control host. These isolation levels or containers can be used to either sandbox specific applications, or to emulate an entirely new host. LXC uses Linux’s cgroups functionality, which was introduced in version 2.6.24 to
3 comments
Read more

How to expose your local server to Internet?

As a developer, we always have a wish to expose our work to internet, so that we can show those to our friends or teachers for testing. But, what we choose to use services of public cloud and sometimes it becomes a bit more expensive way for small projects. So, friends I have found a way to expose your localhost services to the internet without port forwarding through the NAT of your ISP. The solution is: NGROK What is ngrok? Ngrok exposes local servers behind NATs and firewalls to the public internet over secure tunnels. How it works You download and run a program on your machine and provide it the port of a network service, usually a web server. It connects to the ngrok cloud service which accepts traffic on a public address and relays that traffic through to the ngrok process running on your machine and then on to the local address you specified. What it's good for Demoing web sites without deploying Building webhook consumers on your dev machine Testing m
1 comment
Read more