In this blog post I want to point out that I noticed that the IBM Cloud Container Registry is deprecating container builds.
If you don’t know the IBM Cloud Container Registry here are some useful features:
- “Threat insights – It provides advanced capabilities like vulnerability scanning, deployment policy enforcement, and comprehensive risk assessment and prioritization”
- “Integration – It ‘s the IBM Cloud preferred image registry; pre-integrated with the IBM Cloud Kubernetes Service for the DevOps workflow using IBM Open Toolchain or existing a CI/CD toolset.”
- “Security – It’s integrated with Identity and Access Manager and Resource Groups to provide fine-grained access controls to users within the IBM Cloud account.”
For me the deprecation of the container build an is important topic, because it does effect some bash script automations I did in the past.
Here is a short extract of his blog post which fits directly to what I wrote before.
It is very common to use the
cr buildcommand in a DevOps pipeline. In IBM Cloud Continuous Delivery, you can use either Classic pipelines or Tekton pipelines to build container images, but you will need to update existing pipelines to replace the
So, be aware and start your migration for your Container builds now.
- IBM Cloud Registry location :
- IBM Cloud Registry Namespace:
- Container image name and tag:
- Old command with the
ibmcloud cr build -f Dockerfile --tag us.icr.io/cloud-native-suedbro/authors:1 .
2. Replacement using Docker build and push
docker build -t us.icr.io/cloud-native-suedbro/authors:1 .
I hope this was useful for you and let’s see what’s next?
#Kubernetes, #Container, #IBMCloud, #IBMCloudContainerRegistry