diff --git a/.github/workflows/docker-build.yml b/.github/workflows/docker-build.yml
index bc74ad8..f39dd2b 100644
--- a/.github/workflows/docker-build.yml
+++ b/.github/workflows/docker-build.yml
@@ -7,8 +7,14 @@ on:
       - "main"
 
 jobs:
-  DockerBuildAndRelease:
+  Docker_Release:
+    name: "Docker Build And Release"
     runs-on: ubuntu-latest
+    strategy:
+      fail-fast: true
+      matrix:
+        arch: ["amd64", "arm64"]
+        version: ["1.12.2"]
     steps:
       - name: Checkout Repository
         uses: actions/checkout@v4
@@ -32,7 +38,11 @@ jobs:
         uses: docker/build-push-action@v5
         with:
           context: .
+          build-args: |
+            ARCH=${{ matrix.arch }}
+            VERSION=${{ matrix.version }}
           push: true
+          platforms: linux/${{ matrix.arch }}
           tags: registry.dangerous.tech/dangeroustech/zerotierbridge:latest
 
       - name: Generate SBOM
diff --git a/README.md b/README.md
index 6606c2e..947cfa2 100644
--- a/README.md
+++ b/README.md
@@ -42,14 +42,10 @@ Disable bridging by passing `ZT_BRIDGE=false`. This can be done after the initia
 
 If you would like the container to retain the same ZeroTier client ID on reboot, attach a volume as per the below.
 
-`docker run --privileged -e ZT_NETWORKS=NETWORK_ID_HERE ZT_BRIDGE=true --volume zt1:/var/lib/zerotier-one/ zerotierbridge:latest`
+`docker run --privileged -e ZT_NETWORKS=NETWORK_ID_HERE ZT_BRIDGE=true --volume zt_config:/var/lib/zerotier-one/ zerotierbridge:latest`
 
 #### Caveat: Architecture
 
 If you need to run this on a device with different architecture (a raspberry pi, for instance), then just edit line 3 of the Dockerfile.
 
 If you were using a Raspberry Pi 4, you would change this to `ARCH=arm64` and the container will pull the correct ZeroTier installer.
-
-## TODO
-
-- Add kubernetes deployment YAML