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

Kubernetes

59.8K
51.8K
+ 1
681
LXC

118
223
+ 1
19
Add tool

Kubernetes vs LXC: What are the differences?

Introduction

Kubernetes and LXC are both containerization technologies used in the field of cloud computing. While they both serve the purpose of deploying and managing containers, there are several key differences between them.

  1. Container Orchestration: Kubernetes is a container orchestration platform that provides a robust set of tools and features to manage containerized applications. It automates tasks such as deployment, scaling, and load balancing, enabling easier management of containers at scale. On the other hand, LXC is a lightweight virtualization technology that provides operating system-level virtualization. It allows the creation of multiple isolated Linux containers on a single host but lacks the extensive orchestration capabilities of Kubernetes.

  2. Scope of Management: Kubernetes operates at the cluster level, enabling the management of a large number of containers across multiple hosts. It provides mechanisms for service discovery, load balancing, and fault tolerance, allowing applications to scale horizontally. LXC, on the other hand, focuses on managing individual containers within a host. It does not have built-in features for load balancing or horizontal scaling.

  3. Portability: Kubernetes offers a high level of portability, allowing applications to be deployed across different cloud providers or on-premises environments. It provides a unified API and a set of standard deployment manifests (YAML files) that can be used to define and deploy applications. In contrast, LXC is more tied to the underlying host system as it relies on the specific kernel of the host. Moving LXC containers between hosts with different kernels may require additional configuration or compatibility checks.

  4. Resource Sharing: Kubernetes enables efficient resource sharing among containers through its resource management and allocation mechanisms. It provides features like resource quotas, which allow administrators to limit the amount of CPU, memory, and other resources consumed by containers. LXC, on the other hand, does not have built-in resource management capabilities and relies on the host's kernel for resource allocation.

  5. Networking: Kubernetes provides a sophisticated networking model that allows containers to communicate with each other and external services. It supports features like service discovery, load balancing, and network policies for fine-grained control. LXC, being a lower-level technology, primarily relies on the host's networking stack for container networking. While it is possible to configure networking for LXC containers, it lacks the advanced networking features provided by Kubernetes.

  6. Community and Ecosystem: Kubernetes has a vibrant open-source community and a rich ecosystem of third-party tools and integrations. It is widely adopted and supported by major cloud providers. LXC, while also open-source, may not have as extensive a community and ecosystem as Kubernetes. This can result in fewer resources, lesser adoption, and limited support for LXC compared to Kubernetes.

In summary, Kubernetes is a powerful container orchestration platform with advanced features for managing containers at scale, offering greater portability, extensive networking capabilities, and a thriving community. LXC, on the other hand, provides lightweight containerization with a focus on individual container management within a host.

Decisions about Kubernetes and LXC
Michael Roberts

We develop rapidly with docker-compose orchestrated services, however, for production - we utilise the very best ideas that Kubernetes has to offer: SCALE! We can scale when needed, setting a maximum and minimum level of nodes for each application layer - scaling only when the load balancer needs it. This allowed us to reduce our devops costs by 40% whilst also maintaining an SLA of 99.87%.

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.2M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Kubernetes
Pros of LXC
  • 166
    Leading docker container management solution
  • 129
    Simple and powerful
  • 107
    Open source
  • 76
    Backed by google
  • 58
    The right abstractions
  • 25
    Scale services
  • 20
    Replication controller
  • 11
    Permission managment
  • 9
    Supports autoscaling
  • 8
    Simple
  • 8
    Cheap
  • 6
    Self-healing
  • 5
    Open, powerful, stable
  • 5
    Reliable
  • 5
    No cloud platform lock-in
  • 5
    Promotes modern/good infrascture practice
  • 4
    Scalable
  • 4
    Quick cloud setup
  • 3
    Custom and extensibility
  • 3
    Captain of Container Ship
  • 3
    Cloud Agnostic
  • 3
    Backed by Red Hat
  • 3
    Runs on azure
  • 3
    A self healing environment with rich metadata
  • 2
    Everything of CaaS
  • 2
    Gke
  • 2
    Golang
  • 2
    Easy setup
  • 2
    Expandable
  • 2
    Sfg
  • 5
    Easy to use
  • 4
    Lightweight
  • 3
    Simple and powerful
  • 3
    Good security
  • 2
    LGPL
  • 1
    Reliable
  • 1
    Trusted

Sign up to add or upvote prosMake informed product decisions

Cons of Kubernetes
Cons of LXC
  • 16
    Steep learning curve
  • 15
    Poor workflow for development
  • 8
    Orchestrates only infrastructure
  • 4
    High resource requirements for on-prem clusters
  • 2
    Too heavy for simple systems
  • 1
    Additional vendor lock-in (Docker)
  • 1
    More moving parts to secure
  • 1
    Additional Technology Overhead
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is Kubernetes?

    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

    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.

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

    What companies use Kubernetes?
    What companies use LXC?
    Manage your open source components, licenses, and vulnerabilities
    Learn More

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

    What tools integrate with Kubernetes?
    What tools integrate with LXC?

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

    Blog Posts

    Kubernetesetcd+2
    3
    1193
    Dec 8 2020 at 5:50PM

    DigitalOcean

    GitHubMySQLPostgreSQL+11
    3
    2440
    PythonDockerKubernetes+7
    5
    1153
    May 21 2020 at 12:02AM

    Rancher Labs

    KubernetesAmazon EC2Grafana+12
    6
    1530
    Apr 16 2020 at 5:34AM

    Rancher Labs

    KubernetesRancher+2
    3
    971
    What are some alternatives to Kubernetes and LXC?
    Docker Swarm
    Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.
    Nomad
    Nomad is a cluster manager, designed for both long lived services and short lived batch processing workloads. Developers use a declarative job specification to submit work, and Nomad ensures constraints are satisfied and resource utilization is optimized by efficient task packing. Nomad supports all major operating systems and virtualized, containerized, or standalone applications.
    OpenStack
    OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface.
    Rancher
    Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.
    Docker Compose
    With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.
    See all alternatives