Information Technology
Hands on Training icon
Hands On Training
Hands on Training icon

Artifact Registry vs Container Registry

Course Cover
compare button icon

Course Features

icon

Duration

60 minutes

icon

Delivery Method

Online

icon

Available on

Lifetime Access

icon

Accessibility

Desktop, Laptop

icon

Language

English

icon

Subtitles

English

icon

Level

Beginner

icon

Teaching Type

Self Paced

icon

Video Content

60 minutes

Course Description

Lab Details:

This lab explains the differences between Artifact Registry and Google Cloud Container Registry.

Region: us-central1.

Duration: 60 minutes.

What is the Google Cloud Container Registry? ?

Google Cloud Container Registry can be described as a private container image registry that supports OCI and Docker Images. The registry can be accessed in the same way as Docker (push, pull, and manage images from anywhere). GCR uses Google Cloud Storage to store the images at the backend. GCR does not support fine-grained IAM access controls, but you can create IAM roles to Cloud Storage Bucket. Use the standard Docker command line interface to push and pull Docker images into your private Container Registry.

GCR has many advantages

It is tightly integrated with other Google Cloud Services such as Cloud Build and GKE.

Images are kept secure and private.

It caches the most requested Docker Hub images at mirror.gcr.io.

It supports several authentication methods to push and pull images with a third party client.

Vulnerability scanning. You can scan your images for malware.

GCR's disadvantages:

It supports only Multi-Regional Repository.

It is used to store docker images only and does not support other os packages.

What is the Google Cloud Artifact Registry and how does it work?

It is a fully managed Google service that stores Container images and other artifacts. It can store multiple artifacts, such as OS packages for Debian or RPM, as also language packages for popular languages such as Python, Java, Node, and Node.

Artifact Registry has many advantages

Cloud IAM allows for fine-grained access control through Artifact Registry.

You can store your artifacts both regionally and multi-regionally. This is in contrast to Container Registry, which doesn't allow you to store artifacts locally.

It caches the most requested Docker Hub images at mirror.gcr.io.

Supports Pub/Sub notifications, major upgrades in security and scalability and control.

Artifact Registry's disadvantages

GCR is a system that automatically creates a repository after you push an image to the artifact registry. The repository should be manually created before any image is pushed.

Course Overview

projects-img

Virtual Labs

projects-img

Post Course Interactions

projects-img

Hands-On Training

Skills You Will Gain

What You Will Learn

Learn how to create a Docker Container Registry using Google Container Registry

Learn how to create a Docker Container, and Python/Java Artifacts on the Google Artifact Registry

Learn how to access both the Registries

Course Cover