Use multi-arch container images for development (#5045)

Instead of pulling different images from different registries and maintaining a separate Docker Compose file, use images that contain both architectures.
project-koku · Apr 26, 2024 · 506059a · 506059a
1 parent cbadee1
commit 506059a
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 16 deletions.
diff --git a/Makefile b/Makefile
@@ -29,11 +29,7 @@ ifneq ($(DOCKER_COMPOSE_CHECK), 0)
 	DOCKER_COMPOSE_BIN = $(DOCKER)-compose
 endif
 
-# Use ARM images on ARM systems
 DOCKER_COMPOSE = $(DOCKER_COMPOSE_BIN)
-ifeq (arm, $(findstring arm, $(shell uname -m)))
-	DOCKER_COMPOSE = $(DOCKER_COMPOSE_BIN) -f docker-compose.yml -f docker-compose.arm.yml
-endif
 
 # Testing directories
 TESTINGDIR = $(TOPDIR)/testing

diff --git a/docker-compose.arm.yml b/docker-compose.arm.yml
diff --git a/docker-compose.yml b/docker-compose.yml
@@ -614,7 +614,7 @@ services:
 
   hive-metastore:
     container_name: hive-metastore
-    image: quay.io/cloudservices/ubi-hive:3.1.3-metastore-024
+    image: quay.io/samdoran/ubi-hive:3.1.3-metastore-036
     ports:
       - 9083:8000
     environment:
@@ -637,7 +637,7 @@ services:
 
   trino:
     container_name: trino
-    image: quay.io/cloudservices/ubi-trino:443-002
+    image: quay.io/samdoran/ubi-trino:443-002
     user: root
     ports:
       - 8080:8080