Software Alternatives, Accelerators & Startups

runc VS LocalStack

Compare runc VS LocalStack and see what are their differences

runc logo runc

CLI tool for spawning and running containers according to the OCI specification - opencontainers/runc

LocalStack logo LocalStack

LocalStack collects & analyzes the social media activity on every business in America.ย 
  • runc Landing page
    Landing page //
    2023-08-21
  • LocalStack Landing page
    Landing page //
    2020-07-22

runc features and specs

  • Standardization
    runc is part of the Open Containers Initiative (OCI), promoting standardization across container runtimes. This ensures interoperability and broad community support.
  • Lightweight
    As a lightweight and fast CLI tool, runc provides a minimal runtime for environments where resource efficiency is critical.
  • Security
    runc adheres to principles of secure software development and incorporates Linux kernel features like namespaces and cgroups to enhance security.
  • Broad Adoption
    As the reference implementation for OCI, runc is widely adopted and tested in production environments, ensuring reliability.
  • Flexibility
    runc offers the flexibility to handle low-level container configurations, making it suitable for advanced users needing granular control.

Possible disadvantages of runc

  • Complexity for Beginners
    The low-level nature of runc can be daunting for beginners who might prefer higher-level tools like Docker that abstract away complexities.
  • Minimalist Design
    While its simplicity is an advantage, runc lacks some of the advanced features and orchestration capabilities found in other container platforms.
  • Manual Configurations
    Users need to manually handle configurations, which can be error-prone and time-consuming compared to automated solutions.
  • Ecosystem Integration
    runc does not provide direct integration with tools and platforms by default, requiring additional setup for comprehensive ecosystem support.
  • Limited Features
    Compared to complete container platforms, runc offers fewer built-in features, requiring supplementary tools to achieve similar functionalities.

LocalStack features and specs

  • Cost Efficiency
    LocalStack allows developers to emulate AWS services on their local machine, reducing the need for constantly deploying to AWS during the development phase, hence saving on cloud service costs.
  • Development Speed
    By using LocalStack, developers can quickly test and iterate their cloud-based applications locally without the delay of deploying to a remote AWS environment, speeding up the development process.
  • Network Independence
    LocalStack can run entirely offline, meaning that developers are not dependent on internet connectivity while developing and testing AWS cloud services, which is advantageous in network-restricted environments.
  • Isolation
    Running services locally provides an isolated environment for testing, which minimizes the risk of affecting live resources or incurring costs due to accidental cloud service usage.
  • Integration
    LocalStack integrates well with various CI/CD systems, allowing for automated testing and development workflows with simulated AWS services.

Possible disadvantages of LocalStack

  • Service Limitations
    LocalStack does not support all AWS services; some of the less commonly used services may not be available or fully supported, limiting its applicability in certain scenarios.
  • Performance Discrepancies
    The performance characteristics of LocalStack services may differ from their AWS counterparts, which can lead to discrepancies in performance testing and benchmarking.
  • Setup Complexity
    Setting up and maintaining LocalStack can be complex due to dependencies, necessary configurations, and the need for continuous updates to stay in sync with AWS changes.
  • Feature Parity
    As AWS adds new features and updates existing services, it may take time for LocalStack to implement these changes, potentially lagging behind AWS in terms of features.
  • Scaling
    LocalStack is primarily for development and testing on a small scale. It may not replicate the scalability of AWS services, which could limit the feasibility of load testing.

runc videos

2/21/19 RunC Vulnerability Gives Root Access on Container Systems| AT&T ThreatTraq

More videos:

  • Review - Demo MONEY,TIME - RunC

LocalStack videos

AWS LocalStack SQS - Installing AWS LocalStack

More videos:

  • Review - Serverless Localstack Lambda
  • Review - Serverless LocalStack Lambda APIย Gateway

Category Popularity

0-100% (relative to runc and LocalStack)
Web Servers
100 100%
0% 0
Build, Test, Deploy
0 0%
100% 100
Web And Application Servers
AWS Tools
0 0%
100% 100

User comments

Share your experience with using runc and LocalStack. For example, how are they different and which one is better?
Log in or Post with

Social recommendations and mentions

Based on our record, runc seems to be more popular. It has been mentiond 11 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

runc mentions (11)

  • Setup multi node kubernetes cluster using kubeadm
    For kubeadm , kubetlet , kubectl should same version package in this lab I used v1.31 to have 1.31.7 References: Https://kubernetes.io/docs/reference/networking/ports-and-protocols/ Https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ Https://github.com/opencontainers/runc/releases/... - Source: dev.to / over 1 year ago
  • Comparing 3 Docker container runtimes - Runc, gVisor and Kata Containers
    Previously I wrote about the multiple variants of Docker and also the dependencies behind the Docker daemon. One of the dependencies was the container runtime called runc. That is what creates the usual containers we are all familiar with. When you use Docker, this is the default runtime, which is understandable since it was started by Docker, Inc. - Source: dev.to / over 1 year ago
  • You run containers, not dockers - Discussing Docker variants, components and versioning
    Now we have dockerd which uses containerd, but containerd will not create containers directly. It needs a runtime and the default runtime is runc, but that can be changed. Containerd actually doesn't have to know the parameters of the runtime. There is a shim process between containerd and runc, so containerd knows the parameters of the shim, and the shim knows the parameters of runc or other runtimes. - Source: dev.to / almost 2 years ago
  • US Cybersecurity: The Urgent Need for Memory Safety in Software Products
    It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C) As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun), which is written in C as an alternative to runc, which is written in Go( - Source: Hacker News / almost 3 years ago
  • Why did the Krustlet project die?
    Yeah, runtimeClass lets you specify which CRI plugin you want based on what you have available. Here's an example from the containerd documentation - you could have one node that can run containers under standard runc, gvisor, kata containers, or WASM. Without runtimeClass, you'd need either some form of custom solution or four differently configured nodes to run those different runtimes. That's how krustlet did... Source: over 3 years ago
View more

LocalStack mentions (0)

We have not tracked any mentions of LocalStack yet. Tracking of LocalStack recommendations started around Mar 2021.

What are some alternatives?

When comparing runc and LocalStack, you can also consider the following products

Docker Hub - Docker Hub is a cloud-based registry service

AWS Amplify - JavaScript library for app development using cloud services

Apache Thrift - An interface definition language and communication protocol for creating cross-language services.

aws-cli - Universal Command Line Interface for Amazon Web Services

Podman - Simple debugging tool for pods and images

AWS Shell - An integrated shell for working with the AWS CLI. Contribute to awslabs/aws-shell development by creating an account on GitHub.