Use published Docker image in defaults

README.md

@@ -14,7 +14,7 @@ Compatibility target:
 ## Quick start
 
 ```sh
-docker compose up -d --build
+docker compose up -d
 curl -k -H "Accept: application/vnd.koreader.v1+json" https://127.0.0.1:7200/healthcheck
 ```
 
@@ -22,6 +22,9 @@ The compose file stores data in `./data/kosync.sqlite3`, enables user
 registration, exposes HTTPS on `7200`, and exposes plain HTTP on `17200` for
 reverse proxies.
 
+The default compose file uses the published multi-arch image
+`sodium/kosync-rs:v2.1.1`, which supports Linux `amd64` and `aarch64`.
+
 ## Binary usage
 
 ```sh
@@ -78,7 +81,7 @@ container's network namespace.
 scripts/import-from-old-redis.sh \
   --old-container kosync \
   --sqlite ./data/kosync.sqlite3 \
-  --image kosync-rs:latest
+  --image sodium/kosync-rs:v2.1.1
 ```
 
 Then stop the old container and start the new compose stack:
@@ -94,7 +97,7 @@ Export SQLite data back to the old Redis format:
 scripts/export-to-old-redis.sh \
   --old-container kosync \
   --sqlite ./data/kosync.sqlite3 \
-  --image kosync-rs:latest
+  --image sodium/kosync-rs:v2.1.1
 ```
 
 The export script will not flush Redis unless `--flush-target` is passed.

docker-compose.yml

@@ -1,8 +1,6 @@
 services:
   kosync-rs:
-    image: kosync-rs:latest
-    build:
-      context: .
+    image: sodium/kosync-rs:v2.1.1
     container_name: kosync-rs
     restart: unless-stopped
     ports:

scripts/export-to-old-redis.sh

@@ -3,7 +3,7 @@ set -eu
 
 OLD_CONTAINER=kosync
 SQLITE=./data/kosync.sqlite3
-IMAGE=kosync-rs:latest
+IMAGE=sodium/kosync-rs:v2.1.1
 REDIS_URL=redis://127.0.0.1:6379/1
 PULL=1
 FLUSH_TARGET=0

scripts/import-from-old-redis.sh

@@ -3,7 +3,7 @@ set -eu
 
 OLD_CONTAINER=kosync
 SQLITE=./data/kosync.sqlite3
-IMAGE=kosync-rs:latest
+IMAGE=sodium/kosync-rs:v2.1.1
 REDIS_URL=redis://127.0.0.1:6379/1
 PULL=1