From Github to ACI – A tale how to use Visual Studio Team Services & Azure Container Registry for Container CI/CD

Introduction

Today’s post is conceptually a rather simple one… Let’s see how we can go from this ;

To here ;

By using a CI/CD pipeline.

 

Flow of the day

What will we be doing today?

  • Kick-off a VSTS build once a change has been made to our Github repo
    • Build a container via VSTS
    • Publish the container to an ACR (Azure Container Registry)
  • Kick-off a VSTS release once the build succeeded
    • Use an ARM template to deploy an ACI (Azure Container Instance) with our docker container underneath

Sound cool? Let’s get to it!

Continue reading “From Github to ACI – A tale how to use Visual Studio Team Services & Azure Container Registry for Container CI/CD”

Using Visual Studio Team Services & Rancher for continuous deployment for your docker containers

Introduction

Today I’m going to show you how you can leverage the combination of Visual Studio Team Services & Rancher to kickstart your continuous deployment of your docker containers. So every time we update our containers, we want a smooth upgrade process on our container setup. What do you think? Let’s see what this can look like?

 

The flow

The scenario of today will have the following flow ;

  • We’ll use a git(hub) repository to store our docker-compose & rancher-compose file that powers our solution.
  • Next up, we’ll be using VSTS as the orchestrator for your CI/CD-pipeline.
  • Rancher is our preferred container workflow / management tool, and we’ll be using the “rancher-compose” on our VSTS build agent.

Continue reading “Using Visual Studio Team Services & Rancher for continuous deployment for your docker containers”

Issue with VSTS Agent on Ubuntu – Failed to initialize CoreCLR, HRESULT: 0x80131500

So today I was installing an VSTS agent on Ubuntu and I got the following error message ;

Failed to initialize CoreCLR, HRESULT: 0x80131500

I received this error message when trying to run the “config.sh” command ;

2016-12-10-19_22_52-kvaesxdevops-build02_-_tmp_vsts-agent

So how to fix this? Apparently the agent has a hard dependency towards “libicu52”.  By default my system (ubuntu 16.04 LTS) had libicu55 on it. You can find the “old” package on the following location. And install it?

wget http://security.ubuntu.com/ubuntu/pool/main/i/icu/libicu52_52.1-3ubuntu0.5_amd64.deb

sudo dpkg -i libicu52_52.1-3ubuntu0.5_amd64.deb

And that did the trick!

2016-12-10-19_23_01-kvaesxdevops-build02_-_tmp_vsts-agent

Have fun with your Linux CI/CD pipelines now! 😀