# Vagrant Vagrant is a command-line utility for managing the lifecycle of virtual machines and creating reproducible, portable development environments. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Sunsetting netlab Vagrant/libvirt provider DevFeed: [Sunsetting netlab Vagrant/libvirt provider]() Original publisher: [Read original article]() Published: 2026-09-17T05:51:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Vagrant](), [Infrastructure as code](), [Orchestration](), [Containerlab topology](), [Oracle-VM-VirtualBox]() Tags: [change](), [containers](), [infrastructure](), [infrastructure-as-code](), [netlab](), [orchestration](), [vagrant](), [virtualbox]() ### AI overview The netlab project is sunsetting its Vagrant/libvirt provider after the vagrant-libvirt plugin became effectively unmaintained and HashiCorp announced the closure of Vagrant Cloud by the end of 2026. Existing support and tests will remain for now, but no new libvirt features or device integration tests are planned; containerlab will become the primary orchestration path. ### Source excerpt When I started the netlab project, Vagrant was the go-to tool if you wanted to build a virtual environment described in a text configuration file (an idea popularized as infrastructure-as-code). It wasn't ideal for what we were doing, but a tool rarely does a great job when used far away from its intended use case. netlab initially supported Vagrant with VirtualBox, quickly adding support for KVM/libvirt through the vagrant-libvirt plugin. Life was good... until it wasn't. Read more ... ## How vagrant-libvirt Plugin Deals with Duplicate Subnets DevFeed: [How vagrant-libvirt Plugin Deals with Duplicate Subnets]() Original publisher: [Read original article]() Published: 2026-09-16T06:27:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [Vagrant](), [virtual machines](), [Linux](), [Ubuntu]() Tags: [debugging](), [linux](), [vagrant](), [virtual-machines](), [virtualization]() ### AI overview The article explains that vagrant-libvirt can fail when an existing libvirt virtual network has the same IP subnet as the desired management network but a different name. It identifies the resulting network-name mismatch and reports that correcting the network definition in the Vagrantfile resolves the problem. ### Source excerpt TL&DR: Badly. The vagrant-libvirt plugin mysteriously crashes when an existing virtual network (with a different libvirt name) uses the same IP subnet as the desired management network. Background: netlab is using the vagrant-libvirt plugin to manage libvirt/KVM virtual machines with Vagrant. As I already have that infrastructure, I use it to start standalone virtual machines (usually to test various Ubuntu releases) on my Linux server. Things work great... until they don't. Here's how I managed to waste half a day chasing imaginary gremlins caused by a simple error. Read more ... ## Configuring Management IP Addresses to Virtual Network Devices DevFeed: [Configuring Management IP Addresses to Virtual Network Devices]() Original publisher: [Read original article]() Published: 2026-09-14T05:29:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [configuration](), [Orchestration](), [Vagrant](), [Cloud](), [ssh]() Tags: [cli](), [cloud](), [devices](), [dhcp](), [ip](), [ipv4](), [ipv6](), [management](), [netlab](), [network](), [networking](), [orchestration](), [server](), [ssh]() ### AI overview The article explains how to assign predictable management IP addresses to virtual network devices. It contrasts manual console-based setup with automated assignment through orchestration, containers, DHCPv4/DHCPv6, custom Vagrant boxes, and IPv6 mechanisms such as SLAAC. ### Source excerpt It goes without saying that if you want to configure (virtual) network devices with any semi-sane configuration mechanism1, the device must have a working IP address. Here's the time-honored method2 to assign an IP address to a virtual network device: Start the virtual machine (using a GUI)3 Open a new window: either a telnet session to the virtual console port or a full-blown virtual console (GUI) session. Manually configure the IP address, the SSH server, and the user credentials on the first interface. Read more ... ## netlab 26.06: OSPFv3 on FortiOS, MPLS/VPN on SR Linux DevFeed: [netlab 26.06: OSPFv3 on FortiOS, MPLS/VPN on SR Linux]() Original publisher: [Read original article]() Published: 2026-06-08T06:13:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [MPLS VPN](), [Ubuntu](), [Vagrant](), [Script]() Tags: [bugs](), [getting-started](), [github](), [guide](), [improvements](), [installation](), [mpls-vpn](), [netlab](), [release](), [ubuntu](), [upgrade](), [vagrant]() ### AI overview The netlab 26.06 release adds OSPFv3 support on FortiOS and MPLS/VPN support on SR Linux. It also updates installation compatibility for Ubuntu 26.04, includes Vagrant 2.4.9, and contains other improvements and bug fixes. ### Source excerpt netlab release 26.06 adds OSPFv3 support on FortiOS (by @a-v-popov) and MPLS/VPN support on SR Linux. We also ensured the installation scripts work on Ubuntu 26.04 (everything else was OK) and updated the installed Vagrant version to 2.4.9 (we're not using new Vagrant features; you don't have to upgrade it in an existing installation). Other than that, we added a few improvements and squashed a number of bugs. Upgrading or Starting from Scratch? To upgrade your netlab installation, execute pip3 install --upgrade networklab. New to netlab? Start with the Getting Started document and the installation guide. Need help? Open a discussion or an issue in netlab GitHub repository. ## netlab 26.04: EXOS, BGP Prefix Origination, More Static Routes DevFeed: [netlab 26.04: EXOS, BGP Prefix Origination, More Static Routes]() Original publisher: [Read original article]() Published: 2026-04-13T05:28:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [Release notes](), [BGP](), [IP routing](), [Routing (disambiguation)](), [networking](), [Vagrant](), [evpn](), [VXLAN](), [Containerlab topology]() Tags: [bgp](), [evpn](), [ip-routing](), [linux](), [netlab](), [release](), [release-notes](), [routing](), [vagrant](), [vxlan]() ### AI overview The netlab 26.04 release adds support for Extreme Networks EXOS, new BGP advertisement and origination capabilities, additional platforms with static-route support, and EVPN/VXLAN over IPv6 support in FRRouting. It also expands routing configuration support for several platforms. ### Source excerpt netlab release 26.04 is out. Here are the highlights: Extreme Networks EXOS is supported as a Vagrant box or containerlab node with OSPF, VLAN, and VRRP configuration (by Seb d'Argoeuves). The new bgp.advertise node attribute allows you to advertise networks in the IP routing table into BGP. It's supported on most platforms. The bgp.originate attribute is now dual-stack and VRF-aware, allowing you to originate IPv4 and IPv6 prefixes into per-VRF BGP instances. New platforms with static route support: FortiOS (by Aleksey Popov), Nexus OS, Nokia SR OS, Nokia SR Linux. OpenBSD got discard static routes. Read more ... ## Open-Source Network Simulators (2026 Edition) DevFeed: [Open-Source Network Simulators (2026 Edition)]() Original publisher: [Read original article]() Published: 2026-02-10T07:09:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Open Source](), [Vagrant]() Tags: [also](), [netlab](), [network](), [open-source](), [vagrant](), [worth-reading]() ### AI overview The article highlights Brian Linkletter's updated overview of open-source network simulators and emulators. It identifies containerlab and GNS3 as leading options, notes that the original vrnetlab is abandoned, and discusses using netlab primarily with containerlab while gradually phasing out Vagrant support. ### Source excerpt Brian Linkletter published an updated overview of open-source network simulators and emulators. containerlab and GNS3 are clear leaders (no surprise there) with the original vrnetlab becoming abandonware (fortunately, we have Roman Dodin's fork), which makes me think we should focus on using netlab primarily with containerlab and slowly sunset the Vagrant support, particularly considering some people actively hate the license change. Also, if anyone feels like writing an interface (provider module) between netlab and GNS3, the pull request would be most welcome 😎 Read more ... ## Vagrant: entornos de desarrollo reproducibles DevFeed: [Vagrant: entornos de desarrollo reproducibles]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-02-06T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Vagrant](), [Oracle-VM-VirtualBox](), [Linux]() Tags: [ansible](), [hashicorp](), [rsync](), [ruby](), [snapshots](), [vagrant](), [virtualbox]() ### AI overview A Spanish tutorial explaining how Vagrant defines reproducible development environments as code. It covers installation, provider selection, Vagrantfile configuration, the VM lifecycle, SSH access, and synchronized folders, including performance and consistency considerations for VirtualBox, libvirt, NFS, and rsync. ### Source excerpt Vagrant con libvirt o VirtualBox: carpetas sincronizadas, snapshots, aprovisionamiento con Ansible y reload vs provision. ## Molly-Guard: a Lifesaver on a Ubuntu Server DevFeed: [Molly-Guard: a Lifesaver on a Ubuntu Server]() Original publisher: [Read original article]() Published: 2025-07-02T06:18:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Ubuntu](), [Vagrant](), [Cisco](), [Open Source](), [Server](), [Command-line interface]() Tags: [cisco](), [networking](), [open-source](), [ssh](), [terminal](), [ubuntu](), [ubuntu-server](), [vagrant]() ### AI overview The author describes nearly powering off the wrong Ubuntu server instead of a Vagrant VM and recommends the molly-guard package. The package intercepts reboot-related commands during SSH sessions and asks for the target hostname. The article contrasts this safeguard with the lack of an equivalent mechanism on Cisco IOS devices. ### Source excerpt Have you ever managed to type reload in the wrong terminal window and brought down a core switch (I probably did)? I managed to do the Ubuntu equivalent of that stupidity: I told my main Ubuntu server to sudo poweroff instead of doing that to a Vagrant VM. Fortunately, the open-source world doesn't have to rely on the roadmaps created by networking vendors' product managers; if there's a big enough pain, someone will solve it. Read more ... ## Diagnosing MTU Mismatches Between QEMU TAP Interfaces and VM Network Devices DevFeed: [Diagnosing MTU Mismatches Between QEMU TAP Interfaces and VM Network Devices]() Original publisher: [Read original article]() Published: 2025-03-11T07:11:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Linux](), [qemu](), [networking](), [Vagrant](), [Operating system]() Tags: [article](), [connectivity](), [linux](), [networking](), [qemu](), [switching](), [vagrant](), [virtio](), [virtualization]() ### AI overview The article investigates asymmetric connectivity when oversized packets traverse two virtual machines connected through a Linux bridge. Packet captures show that QEMU does not adjust the Linux TAP interface MTU when a VM changes its virtual NIC MTU, creating an MTU mismatch that can prevent packets from reaching the outgoing interface. ### Source excerpt It all started with an innocuous article describing the MTU basics. As the real purpose of the MTU is to prevent packet drops due to fixed-size receiver buffers, and I waste spend most of my time in virtual labs, I wanted to check how various virtual network devices react to incoming oversized packets. As the first step, I created a simple netlab topology in which a single link had a slightly larger than usual MTU... and then all hell broke loose. Read more ... ## Goodbye, Cumulus Community Vagrant Boxes DevFeed: [Goodbye, Cumulus Community Vagrant Boxes]() Original publisher: [Read original article]() Published: 2025-02-19T07:01:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Vagrant](), [Linux](), [VXLAN](), [Pull Request]() Tags: [ci](), [debugging](), [linux](), [netlab](), [nvidia](), [pull-request](), [release](), [ssh](), [vagrant](), [vxlan]() ### AI overview The article describes integration-test failures while reviewing a VXLAN on Cumulus Linux pull request. The failures were traced to Vagrant SSH authentication problems caused by password expiration in Cumulus Community virtual machines. It concludes that newer boxes remain affected, older boxes are outdated, and the Cumulus containers project is no longer maintained. ### Source excerpt Last Monday, I decided to review and merge the "VXLAN on Cumulus Linux 5.x with NVUE" pull request. I usually run integration tests on the modified code to catch any remaining gremlins, but this time, all the integration tests started failing during the VM creation phase. I was completely weirded out, considering everything worked a week ago. Fortunately, Vagrant debugging is pretty good1 and I was quickly able to pinpoint the issue (full printout): Read more ... ## Point-to-Point Links in Virtual Labs DevFeed: [Point-to-Point Links in Virtual Labs]() Original publisher: [Read original article]() Published: 2025-02-12T06:55:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [virtual machines](), [qemu](), [Vagrant](), [Containers](), [Linux](), [Command-line interface]() Tags: [blog-post](), [cli](), [container-networking](), [containers](), [linux](), [netlab](), [networking](), [qemu](), [vagrant](), [virtual-machines](), [virtualization]() ### AI overview This article explains how virtual labs connect virtual machines and Linux containers. It covers UDP tunnels used by KVM/QEMU/libvirt/Vagrant, point-to-point vEth links created by containerlab, and the packet-capture limitations of UDP tunnels. ### Source excerpt In the previous blog post, I described the usual mechanisms used to connect virtual machines or containers in a virtual lab, and the drawbacks of using Linux bridges to connect virtual network devices. In this blog post, we'll see how KVM/QEMU/libvirt/Vagrant use UDP tunnels to connect virtual machines, and how containerlab creates point-to-point vEth links between Linux containers. Read more ... ## Waiting for Network Device Interfaces During netlab Provisioning DevFeed: [Waiting for Network Device Interfaces During netlab Provisioning]() Original publisher: [Read original article]() Published: 2025-02-05T06:59:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [virtual machines](), [Containers](), [Vagrant](), [Ansible](), [qemu](), [ssh]() Tags: [ansible](), [cisco](), [containers](), [netlab](), [network](), [qemu](), [ssh](), [vagrant](), [virtual-machines]() ### AI overview The article explains why netlab must wait for network device interfaces to become operational after virtual machines and containers start. It describes readiness checks for SSH and interfaces, including differences in Cisco Nexus OS and Junos, and outlines how Ansible profiling is used to measure startup delays. ### Source excerpt Once a virtual machine running a network operating system boots, you'd expect its data-plane interfaces to be operational, right? Some vendors disagree. It takes over a minute for some network operating systems to figure out they have this thing called interfaces.1 I would love to figure out what takes them so long (a minute is an eternity on modern CPUs), but I guess we'll never know. Behind the Scenes netlab uses two device provisioning mechanisms: it can start virtual machines with Vagrant or containers with containerlab. Some of those containers might use KVM/QEMU to run a hidden virtual machine (see also: RFC 1925 rule 6a). Read more ... ## Links in Virtual Labs DevFeed: [Links in Virtual Labs]() Original publisher: [Read original article]() Published: 2025-02-03T07:27:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [virtualization](), [networking](), [Linux](), [virtual machines](), [Containers](), [Vagrant]() Tags: [containers](), [ethernet](), [links](), [linux](), [netlab](), [network](), [networks](), [vagrant](), [virtual-machines](), [virtualization]() ### AI overview This article explains how physical network links are represented in virtual labs. It examines virtual bridge switches, Linux bridges, Vagrant and libvirt networks, tap interfaces, and the veth-pair method for connecting containers to Linux bridges. ### Source excerpt There are three major ways to connect network devices in the physical world: Point-to-point links between devices (usually using some variant of Ethernet) Multi-access layer-1 networks running some IEEE 802.x encapsulation on top of that (GPON, WiFi, Ethernet hubs) Multi-access switched layer-2 network (dumb switches, hopefully running some STP variant) Implementing these connections in virtual labs is a bit harder than one might think, as all virtualization solutions assume you plan to run virtual servers connected to Ethernet segments. Read more ... ## How Does Netlab Deal with Server Reboots? DevFeed: [How Does Netlab Deal with Server Reboots?]() Original publisher: [Read original article]() Published: 2024-10-24T06:15:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [Command-line interface](), [Orchestration](), [Vagrant](), [virtual machines](), [Containers](), [Linux]() Tags: [cleanup](), [cli](), [config](), [containers](), [linux](), [netlab](), [orchestration](), [server](), [vagrant](), [virtual-machines]() ### AI overview The article explains that netlab does not automatically recover labs after server reboots, power failures, or crashes because it runs as a CLI rather than a boot-time service. It describes clearing stale locks, restarting virtual-machine labs with snapshot and no-config options, and the more limited recovery options for containers. ### Source excerpt Now and then, someone asks how netlab deals with reboots (or power failures or crashes) of the server it's running on. TL&DR: It doesn't. However... netlab is a CLI command that acts as an umbrella orchestration layer for Vagrant and Containerlab. It does not run as a cron job, init script, or service and thus cannot be invoked when a server is booted. Read more ... ## netlab 1.8.2: Bug Fixes, Usability Improvements DevFeed: [netlab 1.8.2: Bug Fixes, Usability Improvements]() Original publisher: [Read original article]() Published: 2024-05-14T06:01:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [bug](), [Usability](), [configuration](), [Vagrant](), [Docker](), [Ansible](), [Containers]() Tags: [ansible](), [bug](), [bug-fixes](), [configuration](), [containers](), [docker](), [netlab](), [release-notes](), [usability](), [vagrant]() ### AI overview netlab 1.8.2 includes bug fixes, usability improvements, minor changes to device configuration templates, and safeguards for Vagrant boxes, Docker containers, Ansible collections, and modified lab topologies. It also adds minimal Sonic support based on Azure VM images. ### Source excerpt netlab release 1.8.2 contains dozens of bug fixes and minor tweaks to device configuration templates. We also added a few safeguards including: Check for Vagrant boxes or Docker containers before starting the lab and display pointers to build recipes. Check installed Ansible collections before trying to configure the lab devices. Display a warning if the lab topology was modified after the lab was created Read more ... ## Networking Virtual Machines and Containers Must Work Reliably Out of the Box DevFeed: [Networking Virtual Machines and Containers Must Work Reliably Out of the Box]() Original publisher: [Read original article]() Published: 2024-05-06T06:25:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [virtual machines](), [DHCP](), [Vagrant](), [dell]() Tags: [cisco](), [dell](), [dhcp](), [netlab](), [network](), [networking](), [ssh](), [vagrant](), [virtual-machines](), [virtualization]() ### AI overview The article argues that free network operating system images distributed as containers or virtual machines must work reliably out of the box. It describes Junos vPTX rejecting DHCP-assigned addresses and Dell OS10 images having intermittent SSH server failures that make automation and CI/CD use impractical. ### Source excerpt Some networking vendors realized that one way to gain mindshare is to make their network operating systems available as free-to-download containers or virtual machines. That's the right way to go; I love their efforts and point out who went down that path whenever possible1 (as well as others like Cisco who try to make our lives miserable). However, those virtual machines better work out of the box, or you'll get frustrated engineers who will give up and never touch your warez again, or as someone said in a LinkedIn comment to my blog post describing how Junos vPTX consistently rejects its DHCP-assigned IP address: "If I had encountered an issue like this before seeing Ivan's post, I would have definitely concluded that I am doing it wrong."2 Read more ... ## Mobile Testing & Local Dev Sharing with Homestead DevFeed: [Mobile Testing & Local Dev Sharing with Homestead]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-05-06T18:55:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Mobile Testing](), [Vagrant](), [Mobile](), [Development](), [OpenSSH](), [Scripting, bash]() Tags: [environment](), [fantastic](), [here-s](), [homestead](), [hood](), [insights](), [local](), [mobile](), [mobile-testing](), [ngrok](), [share](), [ssh](), [test](), [testing](), [vagrant-homestead](), [want]() ### AI overview A tutorial showing how to use Homestead's share command and Ngrok to expose a local development environment for colleagues or clients, and to test and debug local sites on mobile devices such as an iPhone. ### Source excerpt Homestead is a fantastic local dev environment, but what about when you want to test on mobile or share your local dev environment? Here's how ## Local Development with Vagrant / Homestead DevFeed: [Local Development with Vagrant / Homestead]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-03-31T07:59:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Vagrant](), [Provisioning](), [Web Development](), [Linux](), [Tooling](), [Software Engineering]() Tags: [allows](), [debugging](), [debugging-tools](), [development](), [effectively](), [environment](), [homestead](), [insights](), [linux](), [local](), [modern-web-development](), [projects](), [provisioning](), [safely](), [vagrant](), [vagrant-homestead](), [work]() ### AI overview This tutorial explains how Vagrant/Homestead provides a separate virtual machine for local web development. It discusses safer project workflows, isolated environments, production-like Linux systems, and pre-installed development and debugging tools. ### Source excerpt A local development environment with Vagrant/Homestead allows you to work on projects more safely and effectively ## Using PhpStorm with Vagrant / Homestead DevFeed: [Using PhpStorm with Vagrant / Homestead]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-01-10T22:13:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [phpstorm](), [Vagrant](), [ide](), [PHP](), [Tutorial](), [Content Management System](), [Front end](), [debug]() Tags: [craft](), [dev](), [here-s](), [homestead](), [how-to](), [insights](), [local](), [php](), [phpstorm](), [setup](), [tutorial](), [vagrant](), [vagrant-homestead](), [xdebug]() ### AI overview A tutorial on setting up PhpStorm with Vagrant/Homestead for local PHP development, including guidance for working with Craft CMS and Xdebug. It covers opening an existing project and configuring PhpStorm to use Vagrant. ### Source excerpt Here's how to set up PhpStorm with Vagrant / Homestead for local dev with Xdebug for Craft CMS or other PHP dev ## Ansible on Vagrant - skipping: no hosts matched DevFeed: [Ansible on Vagrant - skipping: no hosts matched]() Original publisher: [Read original article]() Author: Tom Published: 2015-12-29T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Ansible](), [Vagrant](), [Ansible Roles](), [Testing](), [Raspberry Pi]() Tags: [ansible](), [linux](), [raspberry-pi](), [test](), [testing](), [tools](), [vagrant]() ### AI overview This tutorial explains how to resolve Ansible's "no hosts matched" problem when testing playbooks with Vagrant. The issue occurs because the testing machine is not included in the host group defined by the playbook; adding the Vagrant machine to that group in the Vagrantfile resolves it. ### Source excerpt I have some Ansible roles to configure my vps, Raspberry Pi, etc. I like to test them before I broke something on my real, not clustered machines - I use Vagrant for that. But with it I had one problem - in playbooks I define hosts as groups of severs ex. web for my vps: Example Ansible playbook - hosts: web gather_facts: True sudo: True ... But testing machine wasn't in this group and when I run vagrant I could only see: ## Docker at Shopify: How We Built Containers that Power Over 100,000 Online Shops DevFeed: [Docker at Shopify: How We Built Containers that Power Over 100,000 Online Shops]() Original publisher: [Read original article]() Author: Graeme Johnson Published: 2014-11-18T19:22:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Docker](), [Containers](), [Shopify](), [datacenter](), [Ubuntu](), [Vagrant](), [Cloud Native Ecosystem]() Tags: [applications](), [blog](), [building](), [containers](), [cpu](), [data](), [data-center](), [development](), [docker](), [linux](), [local](), [memory](), [operations](), [packages](), [production](), [shopify](), [ubuntu](), [windows]() ### AI overview This Shopify Engineering article explains why Shopify adopted Docker and containerization for its production data center. It presents containers as predictable, fast, self-contained units and discusses bootstrapping, matching the production operating system, using Vagrant for local testing, and choosing thin containers to reduce CPU and memory usage. ### Source excerpt This is the second in a series of blog posts describing our evolution of Shopify toward a Docker-powered, containerized data center. This instalment will focus on the creation of the container used in our production environment when you visit a Shopify storefront. Read the first post in this series here. Why containerize? Before we dive into the mechanics of building containers, let's discuss motivation. Containers have the potential to do for the datacenter what consoles did for gaming. In the early days of PC gaming, each game typically required video or sound driver massaging before you got to play. Gaming consoles however, offered a different experience: predictability: cartridges were self-contained fun: always ready-to-run, with no downloads or updates. fast: cartridges used read-only memory for lightning fast speeds. easy: cartridges were robust and largely child-proof - they were quite literally plug-and-play. Predictable, fast, and easy are all good things at scale. Docker containers provide the building blocks to make our data centers easier to run and more adaptable by placing applications into self-contained, ready-to-run units much like cartridges did for console games.