change mirror order

[Stevesibilia]

PR Type

Enhancement

---

Description

• Reordered Docker registry mirrors to prioritize local mirror over Google Container Registry (GCR) mirror
• Changed the order of --registry-mirror options in the Docker service configuration
• This change aims to improve Docker image pull performance by prioritizing the local mirror
• No other changes were made to the configuration or functionality

---

Changes walkthrough 📝

	Relevant files
Configuration changes	.gitlab-ci-template.yml Optimize Docker registry mirror order                                        templates/.gitlab-ci-template.yml Reordered registry mirrors in Docker service configuration Moved local mirror (127.0.0.1:5000) to higher priority Moved Google Container Registry mirror (mirror.gcr.io) to lower priority +2/-2

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[sparkfabrik-ai-bot]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Key issues to review Performance Impact The reordering of registry mirrors may affect Docker image pull performance. Verify that the local mirror (127.0.0.1:5000) is indeed faster and more reliable than the GCR mirror for your use case.

[sparkfabrik-ai-bot]

PR Code Suggestions ✨

Category	Suggestion	Score
Security	Use HTTPS for all registry mirror URLs Consider using HTTPS for the first registry mirror URL to enhance security. If HTTPS is not available for this mirror, ensure that the connection is secure through other means. templates/.gitlab-ci-template.yml [9-11] "--registry-mirror", -"http://127.0.0.1:5000/spark-int-cloud-services/docker-hub-mirror/", +"https://127.0.0.1:5000/spark-int-cloud-services/docker-hub-mirror/", "--registry-mirror", "https://mirror.gcr.io", Suggestion importance[1-10]: 8 Why: Using HTTPS for all registry mirrors is a crucial security improvement, especially for the local mirror URL which remains unchanged in the PR.	8
	Remove debug mode from Docker daemon configuration Consider removing the --debug=true flag from the Docker daemon command if it's not needed in production. Debug mode can impact performance and potentially expose sensitive information. templates/.gitlab-ci-template.yml [10-15] "--registry-mirror", "https://mirror.gcr.io", "--insecure-registry", "127.0.0.1:5000", -"--debug=true", "--mtu=1460", Suggestion importance[1-10]: 7 Why: Removing debug mode is a good security practice, but the suggestion doesn't account for the actual changes in the PR, which reordered the registry mirrors.	7

[paolomainardi]

LGTM