Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Introduction to Vagrant and Docker

Introduction to Vagrant and Docker

A small introduction for vagrant and Docker.

Avatar for Kuncara Adi Nugraha

Kuncara Adi Nugraha

May 20, 2015
Tweet

More Decks by Kuncara Adi Nugraha

Other Decks in Technology

Transcript

  1. WHY VAGRANT? •  Provides similar development environment across team /

    project •  Reduce development environment setup time •  Increases production / development parity •  Reduce “it works in my machine” issue
  2. CONFIGURATION •  Plain text file (Vagrantfile) •  Ruby DSL • 

    Provisioning Tools : Shell, Puppet, Chef, Salt, Ansible •  Can use similar provisioning with production •  Can be shared and versioned in Source Control
  3. WHAT IS DOCKER? •  Open source engine •  Automates deployment

    applications into container •  Use same linux kernel with host’s
  4. WHY DOCKER? •  Configure Once, Run Anywhere •  Multiple docker

    in a single machine •  Rapid scaling and deployment •  Provide standardize environment in development, staging, and production
  5. CONFIGURATION •  Simple plain text file ( Dockerfile ) • 

    Can be shared and versioned •  Docker Hub
  6. DOCKER VS VAGRANT •  Not Apple to Apple •  Docker

    can run inside Vagrant •  Vagrant allow us to install all we need for development purposes e.g. OS, apps, etc. •  Docker allow us to run self-contained applications with assured libraries and dependencies.