Docker documentation correction (#279)

* Updated `README.md` for new Docker set up

* Set Version: 0.2.3

* Set Version: 0.2.4

---------

Co-authored-by: devops <[email protected]>

README.md

@@ -156,14 +156,17 @@ We provide a Docker image for isolated testing, locally and in CI.
 From the root of the repository:
   - Build the docker image (the `./deps/k_release` file pins the K version):
     ```sh
-    docker build . --build-arg K_COMMIT=$(cat ./deps/k_release) --tag mir-semantics:$(cat ./deps/k_release)
+    docker build . --tag kmir-tests --build-arg K_COMMIT=$(cat deps/k_release) --file .github/workflows/Dockerfile
     ```
    - Run the integration tests in a container:
     ```sh
-    docker run --name mir-semantics --rm -it -u user --workdir /home/user mir-semantics:$(cat ./deps/k_release) make -C kmir test-integration
+    docker run --name kmir-container --rm --interactive --tty --detach --workdir /home/user kmir-tests &&
+    docker cp . kmir-container:/home/user &&
+    docker exec kmir-container chown -R user:user /home/user &&
+    docker exec --user user kmir-container make -C kmir test-integration
     ```
 
-Note: you may need to run the `docker` commands with `sudo`.
+Note: you may need to run the `docker` commands with `sudo`, or start a superuser shell with `sudo -s`..
 
 We use a similar workflow in CI actions defined in the `.github/` directory.
 

kmir/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "poetry.core.masonry.api"
 
 [tool.poetry]
 name = "kmir"
-version = "0.2.3"
+version = "0.2.4"
 description = ""
 authors = [
     "Runtime Verification, Inc. <[email protected]>",

kmir/src/kmir/__init__.py

@@ -2,4 +2,4 @@
 
 from .kmir import KMIR
 
-VERSION: Final = '0.2.3'
+VERSION: Final = '0.2.4'

package/version

@@ -1 +1 @@
-0.2.3
+0.2.4