fix: import backend image into k3s containerd before rollout

docker build only populates the Docker daemon's store; k3s runs its own embedded containerd and never sees it, so imagePullPolicy: Never kept redeploying whatever was last imported instead of new builds. Co-Authored-By: Claude Sonnet 5 <[email protected]>
2026-08-15 16:09:36 +08:00
parent 5def3c14e8
commit 8b1d2f14f1
1 changed files with 7 additions and 0 deletions
@@ -15,6 +15,13 @@ jobs:
      - name: Build backend image
        run: docker build -t realtime-collab-backend:latest ./backend

+      - name: Import image into k3s containerd
+        # docker build only populates the Docker daemon's store; k3s runs its
+        # own containerd (imagePullPolicy: Never, never pulls a registry), so
+        # the image must be explicitly imported or the pod keeps running
+        # whatever was last imported.
+        run: docker save realtime-collab-backend:latest | k3s ctr -n k8s.io images import -
+
      - name: Roll out backend
        run: |
          kubectl rollout restart deployment/realtime-collab-backend