tools/docker: remove abci-harness

The abci-harness image was used to test the terdermint-abci crate
which has been removed in transition to cometbft-rs.

tools/docker/README.md

@@ -43,27 +43,3 @@ Both wallets have an initial signed transaction created for easier population of
 the network before testing. These transactions will send uatom tokens from c0 ->
 c1 and vice versa. They are both signed as `sequence 0` in the wallet, so they
 can only be executed as the first transaction of the corresponding wallet.
-
-## abci-harness
-
-This image is used during CI testing in the abci-rs crate. It tests
-compatibility with the CometBFT Go implementation. It derives from the
-CometBFT Docker image above, but it expects a volume attached at `/abci` that
-contains the ABCI application to be tested. The name of the ABCI application is
-`kvstore-rs` by default. This can be changed by setting the `ABCI_APP`
-environment variable.
-
-The image will fire up a CometBFT node (auto-creating the configuration) and
-then execute the ABCI application from the attached volume. It logs the
-CometBFT node log into kvstore-rs.cometbft and the ABCI application log into
-kvstore-rs.log on the attached volume.
-
-This image has both the `muslc` and `glibc` libraries installed for easy testing
-of dynamically linked binaries.
-
-Example:
-```bash
-docker run -it --rm -v $PWD/target/debug:/abci -p 26657:26657 informaldev/abci-harness:0.34.0
-```
-
-The image version reflects the CometBFT Go binary version.

tools/docker/build-images.sh

@@ -6,13 +6,6 @@ CMTVERSION=${CMTVERSION:-0.34.21}
 
 echo "Building for CometBFT v${CMTVERSION}..."
 
-# Build the ABCI test harness
-docker build \
-    -f abci-harness/Dockerfile \
-    --build-arg CMTVERSION=${CMTVERSION} \
-    --tag informaldev/cometbft:${CMTVERSION} \
-    ./abci-harness/
-
 # Build the CometBFT development image
 docker build \
     -f cometbft/Dockerfile \