Regarding using a mirrored instance of Docker registry: I think even better option would be to cache all images required for ONAP deployment in your on-premise infrastructure, that's what we're doing here at Samsung hence we're not affected by the dockerhub limits.
That would require setting up some automation to download and keep the locally cached image tags up to date but the good news is that there are some handy scripts in offline-installer (Samsung's Onap deployment solution) that you could use. For instance this script https://git.onap.org/oom/offline-installer/tree/build/creating_data/docker-images-collector.sh can be used to enumerate all docker images from OOM project and once you have that list it would be fairly easy to just download them to your local e.g. Nexus repo and leverage on it just like Krzysztof Kosewski suggested. There is even a script here https://git.onap.org/oom/offline-installer/plain/build/build_nexus_blob.sh which given the list of docker images will run a Nexus repository docker container and feed it with images from the list from above script. Then you only have to make sure before each deployment that the tags in your local repo are up to date before ONAP deployment. -- Bartek Grzybowski Samsung R&D Institute Poland Samsung Electronics -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22554): https://lists.onap.org/g/onap-discuss/message/22554 Mute This Topic: https://lists.onap.org/mt/78360010/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
