Alternatives to Amazon ECR logo

Alternatives to Amazon ECR

Docker Hub, Kubernetes, Harbor, Quay.io, and Amazon Elastic Container Registry Public are the most popular alternatives and competitors to Amazon ECR.
324
148
+ 1
5

What is Amazon ECR and what are its top alternatives?

It is a fully managed container registry that makes it easy to store, manage, share, and deploy your container images and artifacts anywhere. It eliminates the need to operate your own container repositories or worry about scaling the underlying infrastructure.
Amazon ECR is a tool in the Docker Registry category of a tech stack.

Top Alternatives to Amazon ECR

  • Docker Hub
    Docker Hub

    It is the world's easiest way to create, manage, and deliver your teams' container applications. It is the perfect home for your teams' applications. ...

  • Kubernetes
    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. ...

  • Harbor
    Harbor

    Harbor is an open source cloud native registry that stores, signs, and scans container images for vulnerabilities. Harbor solves common challenges by delivering trust, compliance, performance, and interoperability. It fills a gap for organ ...

  • Quay.io
    Quay.io

    Simply upload your Dockerfile (and any additional files it needs) and we'll build your Dockerfile into an image and push it to your repository. ...

  • Amazon Elastic Container Registry Public
    Amazon Elastic Container Registry Public

    It is a fully managed registry that makes it easy for a developer to publicly share container software worldwide for anyone to download. Anyone (with or without an AWS account) can use it to pull container software for use. Amazon ECR Public Gallery is a website that allows anyone to browse and search for public container images, view developer-provided details, and see pull commands. Developers no longer need to use different private and public registries when building and sharing their public container artifacts. ...

  • Kraken by Uber
    Kraken by Uber

    A P2P-powered Docker registry that focuses on scalability and availability. It is designed for Docker image management, replication and distribution in a hybrid cloud environment. ...

  • Gandalf
    Gandalf

    We provide a secure private registry where users can host their docker images and share them privately and securely within teams. ...

Amazon ECR alternatives & related posts

Docker Hub logo

Docker Hub

219
240
6
Build and Ship any Application Anywhere
219
240
+ 1
6
PROS OF DOCKER HUB
  • 1
    Provides public and private repositories
  • 1
    Uses a very familiar collaboration model as GitHub, the
  • 1
    Quickly creates organizations, add users or create grou
  • 1
    Allows users to set permissions to restrict access or s
  • 1
    Fairly inexpensive with usage based pricing
  • 1
    Security scanning available
CONS OF DOCKER HUB
  • 1
    Lacks fine grain access control
  • 1
    Does not provide any insight into the registry usage
  • 1
    Lacks LDAP, SAML and OAuth support

related Docker Hub posts

Shared insights
on
Amazon ECRAmazon ECRDocker HubDocker Hub

We have been using Docker Hub free plan for some time, which had automated builds feature included in the free plan. Recently it has been removed from the free plan. Therefore we have thought to either go ahead with a paid plan of Docker Hub, which includes automated builds feature or migrate to use Amazon ECR as the container registry management solution. Since we already use some AWS services, going ahead with Amazon ECR is a viable solution. I am a bit confused as to what would be the best choice going ahead. Please advice...!

See more
Kubernetes logo

Kubernetes

49.9K
43.4K
639
Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops
49.9K
43.4K
+ 1
639
PROS OF KUBERNETES
  • 162
    Leading docker container management solution
  • 126
    Simple and powerful
  • 104
    Open source
  • 75
    Backed by google
  • 56
    The right abstractions
  • 24
    Scale services
  • 19
    Replication controller
  • 10
    Permission managment
  • 7
    Simple
  • 7
    Cheap
  • 7
    Supports autoscaling
  • 4
    Reliable
  • 4
    Self-healing
  • 4
    No cloud platform lock-in
  • 3
    Quick cloud setup
  • 3
    Open, powerful, stable
  • 3
    Scalable
  • 3
    Promotes modern/good infrascture practice
  • 2
    Captain of Container Ship
  • 2
    A self healing environment with rich metadata
  • 2
    Cloud Agnostic
  • 2
    Runs on azure
  • 2
    Backed by Red Hat
  • 2
    Custom and extensibility
  • 1
    Golang
  • 1
    Expandable
  • 1
    Gke
  • 1
    Easy setup
  • 1
    Sfg
  • 1
    Everything of CaaS
CONS OF KUBERNETES
  • 15
    Poor workflow for development
  • 15
    Steep learning curve
  • 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

related Kubernetes posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.5M views

How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

https://eng.uber.com/distributed-tracing/

(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

See more
Yshay Yaacobi

Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

See more
Harbor logo

Harbor

147
157
11
Manage and serve container images in a secure environment (created at VMware)
147
157
+ 1
11
PROS OF HARBOR
  • 4
    Good on-premises container registry
  • 1
    Container Replication
  • 1
    Nice UI
  • 1
    Vulnerability Scanner
  • 1
    Supports LDAP/Active Directory
  • 1
    Supports OIDC
  • 1
    Support multiple authentication methods
  • 1
    Perfect for Teams and Organizations
CONS OF HARBOR
    Be the first to leave a con

    related Harbor posts

    Quay.io logo

    Quay.io

    63
    76
    7
    Secure hosting for private Docker repositories
    63
    76
    + 1
    7
    PROS OF QUAY.IO
    • 6
      Great UI
    • 1
      API
    • 0
      Docker cloud repositories are public by default. Bad
    CONS OF QUAY.IO
      Be the first to leave a con

      related Quay.io posts

      Amazon Elastic Container Registry Public logo

      Amazon Elastic Container Registry Public

      13
      4
      0
      Fully managed registry that makes it easy for a developer to publicly share container software
      13
      4
      + 1
      0
      PROS OF AMAZON ELASTIC CONTAINER REGISTRY PUBLIC
        Be the first to leave a pro
        CONS OF AMAZON ELASTIC CONTAINER REGISTRY PUBLIC
          Be the first to leave a con

          related Amazon Elastic Container Registry Public posts

          Kraken by Uber logo

          Kraken by Uber

          7
          39
          3
          P2P Docker registry capable of distributing TBs of data in seconds
          7
          39
          + 1
          3
          PROS OF KRAKEN BY UBER
          • 3
            Scalability and replication of TB's in a second.
          CONS OF KRAKEN BY UBER
            Be the first to leave a con

            related Kraken by Uber posts

            Gandalf logo

            Gandalf

            3
            9
            0
            Affordable Docker Private Registries
            3
            9
            + 1
            0
            PROS OF GANDALF
              Be the first to leave a pro
              CONS OF GANDALF
                Be the first to leave a con

                related Gandalf posts