Pushing Docker images to the Docker registry
About this task
The Component Pack Helm charts use a Docker registry to pull the Docker images to run the associated pods. The required Docker images are included in the Component Pack installation package; as part of the Component Pack deployment process, you must push the Docker images to your Docker registry.
Procedure
-
Determine which Docker images you need for your Component Pack deployment.
Table 1 lists the Docker images required by the Helm chart that installs each of the Component Pack offerings.
Table 1. Docker images required by each Helm chart Helm chart Repository/image bootstrap
connections/bootstrap infrastructure
connections/appregistry-client
connections/appregistry-service
connections/middleware/haproxy
connections/middleware/mongodb
connections/middleware/mongodb-rs-setup
connections/middleware/redis
connections/middleware/redis-sentinelorientme
connections/analysis-service
connections/community-suggestions
connections/indexing-service
connections/itm-services
connections/mail-service
connections/middleware-graphql
connections/orient-web-client
connections/people/people-datamigration
connections/people/people-idmapping
connections/people/people-relationship
connections/people/people-scoring
connections/retrieval-service
connections/middleware/solr-basic
connections/userprefs-service
connections/middleware/zookeeperelasticsearch
connections/elasticsearch mw-proxy
connections/mw-proxy elasticstack
connections/elasticsearch-curator
connections/filebeat
connections/kibana
connections/logstashsanity
connections/sanity sanity-watcher
connections/sanity-watcher cnx-ingress
connections/cnx-ingress Note: If you are using Amazon ECR, then before you can push the Docker images, you must create the repository to store them. Use Table 1 to determine the required repository for each of the images. -
Run the following command to push the images to the Docker registry.