Use fully qualified image names #3023
Labels
🤖 aspect: dx
Concerns developers' experience with the codebase
✨ goal: improvement
Improvement to an existing user-facing feature
help wanted
Open to participation from the community
🟨 priority: medium
Not blocking but should be addressed soon
🧱 stack: mgmt
Related to repo management and automations
Current Situation
We use unqualified image names in our Dockerfiles and docker-compose files.
Here's a note from Podman explaining which this is not generally a good idea:
In other words, it's too easy for the wrong image to be pulled. On machines where multiple default registeries are configured,
just up
will hang while the docker backend asks which registry to pull each unqualified images from.Suggested Improvement
Switch to using fully qualified image names, e.g., instead of
airflow
->docker.io/apache/airflow
and so on. This would need to be applied to essentially all of our images (except Elasticsearch, because we already pull it from a non-default registry anyway).Benefit
Reduced ambiguity, reduced chance of the incorrect image working, eliminate issues on machines configured with multiple default search registries.
The text was updated successfully, but these errors were encountered: