Welcome to this lesson on Oracle Cloud Infrastructure Registry, also referred to as Container Registry or OCIR. What is container registry? It's a highly available Docker container registry service. It stores Docker images in private or public repositories, and it runs as a fully managed service on Oracle Cloud Infrastructure. Now what problem does it solve? Without a managed registry, it is hard for development and operations team to maintain a consistent set of images for their containerized application. It's also pretty hard to enforce access rights and have the right security policies without having a container registry. A bunch of these applications can be deployed globally, so it's hard to find the right images and have them available in the region of choice or region of deployment without having a container registry. Now, basically what it does it makes it easy for you as a developer to store, share, and manage container images, such as Docker images. Now, you can use container registry both as a private Docker registry for internal use, you can push and pull Docker images from the container registry using the standard Docker CLI. Or you could use container registry as a public Docker registry enabling any user with Internet access to pull images from public repositories in container registry. You can use it both as a private registry as well as a public registry. As we discussed it basically makes it easy for you as a developer to store, share, and manage these images, and the graphics on this page just show that. You can push images to the registry and then you could deploy these images globally in any region of your deployment choice. Now what are these things called repository? That's the registry, it could be a private or a public registry. It's a Docker compliant registry for your images. Now, what are these things called repositories? As you can see on the screen, a repository is basically, it's a name in container registry from which you can push and pull images. Think about this as a meaningfully named collection of related images grouped together. Typically, what you would do is you will group together different versions of the same source image into the same repository. Each image in the repository is uniquely identified by the combination of its repository name and it's tagged. As you create a repo here, short for repository, you can make them either private or public, same as registry you can decide to make these as private or public, so you get that option here. Now, you see this thing called image, but the whole idea is to store images within these repos, and then you access these images because you can push these images to the repository and then you can pull these images. You need to access these images, and you access them using this thing called image path, like a fully qualified path here. You can see the syntax for the path it has the region key. There is a reserved keyword here. There's a tenancy, namespace, and then there is a repo name, and there is a tag. This is the fully qualified path for the images. You see a couple of examples here. These are both running in Ashburn region, so the region key is iad, and this is the reserved keyword. This is my tenancy namespace, and then project 01/acme-web-app is the name of my repo. Then version1 is basically a way for we have our tag. A tag is basically a string used to refer to a particular image in unknown repository, so there is version1, version2. Now, the reason I'm showing you this is when you use container registry, the main takeaway from here is to have these images stored and you access them using these fully qualified image path. Then the service is fully integrated with the OKE, Oracle Container Engine for Kubernetes. During the deployment of an application to a Kubernetes cluster, you will pull images from the container registry. In the application's manifest file, you specify the images to pull with a path and credential to use when pulling the images. That's why it's critical to know the syntax of the path because this is what you would use in your Kubernetes credential files. This service is also integrated with functions because that also uses Docker images to run your code base. That's in a nutshell all about container registry. Remember it makes it easy for you as a developer to store, share, and manage container images like Docker images. I hope you found this lesson useful. Thanks for your time.
