We need to re-tag the images because when you push an image to a registry, the image full name format must be REGISTRYNAME\IMAGENAME:TAG.
We generate the image with no registry name, so it only has the IMAGENAME:TAG part. When we push to a registry, we need to re-tag it to ad dthe REGISTRYNAME part.
To deploy the image, it would depend on what are you going to deploy to (i.e. Kubernetes, Docker Swarm, OpenShift, CloudFoundry, etc) because each one has it's own way, including different commands, toolsets, etc. And there may even be multiple ways to deploy to the same cluster (in K8S, for example, you can use the yaml definitions, the kubectl command, or yet something like helm) :)
Thank you Davide for the response. One thing I noticed when I initially built the image is..Image name is appended with container registry name. Example in my case would be quay.apps.ocp.com/cmdiscovery. Looks like this is happening when I login to container registry before building the image. Is this intended behavior or as I am missing something?
We need to re-tag the images because when you push an image to a registry, the image full name format must be
REGISTRYNAME\IMAGENAME:TAG.We generate the image with no registry name, so it only has the
IMAGENAME:TAGpart. When we push to a registry, we need to re-tag it to ad dtheREGISTRYNAMEpart.To deploy the image, it would depend on what are you going to deploy to (i.e. Kubernetes, Docker Swarm, OpenShift, CloudFoundry, etc) because each one has it's own way, including different commands, toolsets, etc. And there may even be multiple ways to deploy to the same cluster (in K8S, for example, you can use the yaml definitions, the kubectl command, or yet something like helm) :)
Thank you Davide for the response. One thing I noticed when I initially built the image is..Image name is appended with container registry name. Example in my case would be quay.apps.ocp.com/cmdiscovery. Looks like this is happening when I login to container registry before building the image. Is this intended behavior or as I am missing something?
Uhm, not sure… never seen that happening 😅 perhaps they may have changed the way the task work.. I will try to reproduce that behavior