Switch to tagged spi-base

Author: finestructure

.devcontainer/Dockerfile

@@ -1,4 +1,4 @@
-FROM registry.gitlab.com/finestructure/spi-base:ebce5430b5d53e41b5f178fc39fbd5456c53f2ac
+FROM registry.gitlab.com/finestructure/spi-base:2.2.0
 
 # Install SPM build dependencies
 RUN apt-get update && apt-get install -y curl git make unzip \

.github/workflows/ci.yml

@@ -29,7 +29,7 @@ jobs:
     name: Test
     runs-on: ubuntu-latest
     container:
-      image: registry.gitlab.com/finestructure/spi-base:ebce5430b5d53e41b5f178fc39fbd5456c53f2ac
+      image: registry.gitlab.com/finestructure/spi-base:2.2.0
       options: --privileged
     steps:
       - name: GH Runner bug workaround
@@ -141,7 +141,7 @@ jobs:
     name: Release build
     runs-on: ubuntu-latest
     container:
-      image: registry.gitlab.com/finestructure/spi-base:ebce5430b5d53e41b5f178fc39fbd5456c53f2ac
+      image: registry.gitlab.com/finestructure/spi-base:2.2.0
       options: --privileged
     steps:
       - name: GH Runner bug workaround

.github/workflows/query-performance.yml

@@ -28,7 +28,7 @@ jobs:
     runs-on: ubuntu-latest
     continue-on-error: true
     container:
-      image: registry.gitlab.com/finestructure/spi-base:ebce5430b5d53e41b5f178fc39fbd5456c53f2ac
+      image: registry.gitlab.com/finestructure/spi-base:2.2.0
     steps:
       - name: Checkout code
         uses: actions/checkout@v6

Dockerfile

@@ -18,7 +18,7 @@
 # ================================
 # Build image
 # ================================
-FROM registry.gitlab.com/finestructure/spi-base:ebce5430b5d53e41b5f178fc39fbd5456c53f2ac AS build
+FROM registry.gitlab.com/finestructure/spi-base:2.2.0 AS build
 
 # Set up a build area
 WORKDIR /build
@@ -65,7 +65,7 @@ RUN [ -d /build/Resources ] && { mv /build/Resources ./Resources && chmod -R a-w
 # ================================
 # Run image
 # ================================
-FROM registry.gitlab.com/finestructure/spi-base:ebce5430b5d53e41b5f178fc39fbd5456c53f2ac
+FROM registry.gitlab.com/finestructure/spi-base:2.2.0
 
 # NB sas 2022-09-23: We're not using a dedicated `vapor` user to run the executable, because it
 # makes managing the data in the checkouts volume difficult. See

LOCAL_DEVELOPMENT_SETUP.md

@@ -238,7 +238,7 @@ The trickiest part of this is to ensure the test or app container can connect to
 So, in order to run the tests in a Linux container run:
 
 ```
-docker run --rm -v "$PWD":/host -w /host --add-host=host.docker.internal:host-gateway registry.gitlab.com/finestructure/spi-base:ebce5430b5d53e41b5f178fc39fbd5456c53f2ac swift test
+docker run --rm -v "$PWD":/host -w /host --add-host=host.docker.internal:host-gateway registry.gitlab.com/finestructure/spi-base:2.2.0 swift test
 ```
 
 Make sure you use the most recent `spi-base` image. You can find the latest image name in the `test-docker` target, which also provides a convenient way to run all all tests in a docker container.

Makefile

@@ -89,7 +89,7 @@ test-docker:
 	@# run tests inside a docker container
 	docker run --rm -v "$(PWD)":/host -w /host \
 	  --add-host=host.docker.internal:host-gateway \
-	  registry.gitlab.com/finestructure/spi-base:ebce5430b5d53e41b5f178fc39fbd5456c53f2ac \
+	  registry.gitlab.com/finestructure/spi-base:2.2.0 \
 	  make test
 
 test-e2e: db-reset reconcile ingest analyze