8f44cd35d8
Previously IDs of container images were gotten from tar files of container images but that way was wrong. If multiple json files are contained in a tar file, the script got multiple IDs and tried to pass these IDs on `docker tag` command. Then the command was failed. This updates the script to get image IDs from `docker image inspect` command to fix this issue. In addition, this adds a check a registry container exists already or not before deploying registry container to avoid a container conflict failure. |
||
|---|---|---|
| .. | ||
| README.md | ||
| docker-daemon.json | ||
| generate_list.sh | ||
| manage-offline-container-images.sh | ||
| registries.conf | ||
README.md
Offline deployment
manage-offline-container-images.sh
Container image collecting script for offline deployment
This script has two features: (1) Get container images from an environment which is deployed online. (2) Deploy local container registry and register the container images to the registry.
Step(1) should be done online site as a preparation, then we bring the gotten images to the target offline environment. Then we will run step(2) for registering the images to local registry.
Step(1) can be operated with:
manage-offline-container-images.sh create
Step(2) can be operated with:
manage-offline-container-images.sh register
generate_list.sh
This script generates the list of downloaded files and the list of container images by roles/download/defaults/main.yml file.
Run this script will generates three files, all downloaded files url in files.list, all container images in images.list, all component version in generate.sh.
bash generate_list.sh
tree temp
temp
├── files.list
├── generate.sh
└── images.list
0 directories, 3 files
In some cases you may want to update some component version, you can edit generate.sh file, then run bash generate.sh | grep 'https' > files.list to update file.list or run bash generate.sh | grep -v 'https'> images.list to update images.list.