Container registries
This local console is not CrowdStrike production. Registries you see stay on this clone. They do not come from a Falcon tenant and they do not call Falcon cloud. This is not CrowdStrike Falcon Container cloud.
Sign in first. Follow Signing in to the console with
[email protected], then use the left rail.
Container registries
Choose Container registries in the rail. The table lists the seed registries for this CID (id, type, url, and user-defined alias):
| id | type | url | user_defined_alias |
|---|---|---|---|
| reg-lab-1 | docker | docker.io | lab-docker |
| reg-lab-2 | docker | ghcr.io | lab-ghcr |
Enter type docker, url quay.io, and alias lab-quay, then
Create registry. The table includes reg-lab-quay with type
docker, url quay.io, and alias lab-quay.
Enter id reg-lab-2, then Delete registry. The table no longer
includes reg-lab-2. reg-lab-1 remains.
Enter id reg-lab-1 and alias lab-docker-b, then Update
registry. The table shows reg-lab-1 with alias lab-docker-b. Type
and url stay docker and docker.io.
Open reg-lab-1. Detail shows id, type, url, user-defined alias, and CID.
Container registries is not Container images, not Container vulnerabilities, not Kubernetes, and not Registry creds. Container images stay on Container images. Combined container vulnerabilities stay on Container vulnerabilities. Kubernetes stays on Kubernetes. Registry creds is a separate page: Registry creds.