kata-containers/rust-vmm-ci
1
0
Fork 0
mirror of https://github.com/rust-vmm/rust-vmm-ci.git synced 2026-08-05 03:08:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

README: use latest container tag in the examples

Browse Source 
We recently changed the container tags from vNN to gSHA-1, but we didn't
update README.md. Also, we now push `latest`, which is always updated,
so use this tag in the examples and mention to look at CONTAINER_VERSION
in .buildkite/autogenerate_pipeline.py for a specific version.

Reported-by: Hanna Czenczek <hreitz@redhat.com>
Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
This commit is contained in:
Stefano Garzarella
2025-07-30 17:02:30 +02:00
parent 659de9e3a1
commit a5d88d4f8f
1 changed files with 17 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
README.md
View File

@@ -163,7 +163,7 @@ steps:
platform: x86_64.metal platform: x86_64.metal
plugins: plugins:
- docker#v3.8.0: - docker#v3.8.0:
image: rustvmm/dev:v16 image: rustvmm/dev:latest
always-pull: true always-pull: true
timeout_in_minutes: 5 timeout_in_minutes: 5
``` ```
@@ -244,14 +244,15 @@ coverage before submitting a PR, run the coverage test:
```bash ```bash
CRATE="kvm-ioctls" CRATE="kvm-ioctls"
# NOTE: This might not be the latest container version, you can check which one we're using # NOTE: `latest` should point to the latest version, but you can specify an exact
# by looking into the .buildkite/autogenerate_pipeline.py file. # one as we do with CONTAINER_VERSION in .buildkite/autogenerate_pipeline.py file.
LATEST=16 TAG="latest"
docker pull rustvmm/dev:${TAG}
docker run --device=/dev/kvm \ docker run --device=/dev/kvm \
-it \ -it \
--security-opt seccomp=unconfined \ --security-opt seccomp=unconfined \
--volume $(pwd)/${CRATE}:/${CRATE} \ --volume $(pwd)/${CRATE}:/${CRATE} \
rustvmm/dev:v${LATEST} rustvmm/dev:${TAG}
cd ${crate} cd ${crate}
pytest --profile=devel rust-vmm-ci/integration_tests/test_coverage.py pytest --profile=devel rust-vmm-ci/integration_tests/test_coverage.py
``` ```
@@ -292,7 +293,7 @@ steps:
platform: arm.metal platform: arm.metal
plugins: plugins:
- docker#v3.8.0: - docker#v3.8.0:
image: rustvmm/dev:v16 image: rustvmm/dev:latest
always-pull: true always-pull: true
``` ```
@@ -330,11 +331,15 @@ pipeline output. In its present form, the test cannot fail.
To run the test locally: To run the test locally:
```bash ```bash
# NOTE: `latest` should point to the latest version, but you can specify an exact
# one as we do with CONTAINER_VERSION in .buildkite/autogenerate_pipeline.py file.
TAG="latest"
docker pull rustvmm/dev:${TAG}
docker run --device=/dev/kvm \ docker run --device=/dev/kvm \
-it \ -it \
--security-opt seccomp=unconfined \ --security-opt seccomp=unconfined \
--volume $(pwd)/${CRATE}:/${CRATE} \ --volume $(pwd)/${CRATE}:/${CRATE} \
rustvmm/dev:v${LATEST} rustvmm/dev:${TAG}
cd ${CRATE} cd ${CRATE}
pytest rust-vmm-ci/integration_tests/test_benchmark.py -s pytest rust-vmm-ci/integration_tests/test_benchmark.py -s
``` ```
@@ -351,14 +356,15 @@ that autogenerates the pipeline. For example:
```bash ```bash
cd ~/vm-superio cd ~/vm-superio
CRATE="vm-superio" CRATE="vm-superio"
# NOTE: This might not be the latest container version, you can check which one we're using # NOTE: `latest` should point to the latest version, but you can specify an exact
# by looking into the .buildkite/autogenerate_pipeline.py file. # one as we do with CONTAINER_VERSION in .buildkite/autogenerate_pipeline.py file.
LATEST=16 TAG="latest"
docker pull rustvmm/dev:${TAG}
docker run -it \ docker run -it \
--security-opt seccomp=unconfined \ --security-opt seccomp=unconfined \
--volume $(pwd):/${CRATE} \ --volume $(pwd):/${CRATE} \
--volume ~/.ssh:/root/.ssh \ --volume ~/.ssh:/root/.ssh \
rustvmm/dev:v${LATEST} rustvmm/dev:${TAG}
cd vm-superio cd vm-superio
./rust-vmm-ci/test_run.py ./rust-vmm-ci/test_run.py
``` ```