Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

LXC
LXC

50
53
+ 1
7
VMware vSphere
VMware vSphere

263
167
+ 1
25
Add tool

LXC vs VMware vSphere: What are the differences?

LXC: Linux containers. LXC is a userspace interface for the Linux kernel containment features. Through a powerful API and simple tools, it lets Linux users easily create and manage system or application containers; VMware vSphere: Free bare-metal hypervisor that virtualizes servers so you can consolidate your applications on less hardware. vSphere is the world’s leading server virtualization platform. Run fewer servers and reduce capital and operating costs using VMware vSphere to build a cloud computing infrastructure.

LXC can be classified as a tool in the "Virtual Machine Platforms & Containers" category, while VMware vSphere is grouped under "Virtualization Platform".

LXC is an open source tool with 2.66K GitHub stars and 797 GitHub forks. Here's a link to LXC's open source repository on GitHub.

MIT, CircleCI, and Accenture are some of the popular companies that use VMware vSphere, whereas LXC is used by Robinhood, Wiser., and Platform.sh. VMware vSphere has a broader approval, being mentioned in 56 company stacks & 24 developers stacks; compared to LXC, which is listed in 11 company stacks and 5 developer stacks.

- No public GitHub repository available -

What is LXC?

LXC is a userspace interface for the Linux kernel containment features. Through a powerful API and simple tools, it lets Linux users easily create and manage system or application containers.

What is VMware vSphere?

vSphere is the world’s leading server virtualization platform. Run fewer servers and reduce capital and operating costs using VMware vSphere to build a cloud computing infrastructure.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose LXC?
Why do developers choose VMware vSphere?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
      Be the first to leave a con
      What companies use LXC?
      What companies use VMware vSphere?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with LXC?
      What tools integrate with VMware vSphere?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to LXC and VMware vSphere?
      Docker
      The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere
      LXD
      LXD isn't a rewrite of LXC, in fact it's building on top of LXC to provide a new, better user experience. Under the hood, LXD uses LXC through liblxc and its Go binding to create and manage the containers. It's basically an alternative to LXC's tools and distribution template system with the added features that come from being controllable over the network.
      KVM
      KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V).
      Vagrant Cloud
      Vagrant Cloud pairs with Vagrant to enable access, insight and collaboration across teams, as well as to bring exposure to community contributions and development environments.
      rkt
      Rocket is a cli for running App Containers. The goal of rocket is to be composable, secure, and fast.
      See all alternatives
      Decisions about LXC and VMware vSphere
      Tymoteusz Paul
      Tymoteusz Paul
      Devops guy at X20X Development LTD · | 12 upvotes · 196.1K views
      Amazon EC2
      Amazon EC2
      LXC
      LXC
      CircleCI
      CircleCI
      Docker
      Docker
      Git
      Git
      Vault
      Vault
      Apache Maven
      Apache Maven
      Slack
      Slack
      Jenkins
      Jenkins
      TeamCity
      TeamCity
      Logstash
      Logstash
      Kibana
      Kibana
      Elasticsearch
      Elasticsearch
      Ansible
      Ansible
      VirtualBox
      VirtualBox
      Vagrant
      Vagrant

      Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

      It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

      I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

      We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

      If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

      The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

      Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

      See more
      Interest over time
      Reviews of LXC and VMware vSphere
      No reviews found
      How developers use LXC and VMware vSphere
      Avatar of ShadowICT
      ShadowICT uses VMware vSphereVMware vSphere

      We use VMWare vSphere to allow us to virtualise our environment. This means that we don't have to have as many physical servers to split our infrastructure as we would otherwise. vSphere also enables us to move our virtual machines between different servers as required such as if we need to perform essential maintenance on a host while keeping to our belief of having high availability of all of our services wherever possible.

      Avatar of The Independent
      The Independent uses VMware vSphereVMware vSphere

      vSphere provides a central management interface for the entire stack. In addition to application level redundancy, VM level redundancy is offered through HA and DRS.

      Avatar of POROWNEO.PL
      POROWNEO.PL uses VMware vSphereVMware vSphere

      Hypervisor used in a private cloud platform

      Avatar of Codeweavers Ltd
      Codeweavers Ltd uses VMware vSphereVMware vSphere

      Hybrid Physical/Virtual Datacentre

      How much does LXC cost?
      How much does VMware vSphere cost?
      Pricing unavailable
      News about LXC
      More news
      News about VMware vSphere
      More news