From 15401ddc54857223b9255dae674384f4ca2777ef Mon Sep 17 00:00:00 2001 From: Jakub Al-Khalili Date: Thu, 28 Nov 2019 10:04:03 +0100 Subject: [PATCH] Update docs - change CR to CONTAINER_RUNTIME, IMAGE_PULL_MODE in .env notice --- .../content/en/docs/Getting Started/future/developer-guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/en/docs/Getting Started/future/developer-guide.md b/website/content/en/docs/Getting Started/future/developer-guide.md index dcbbb926..65f20919 100644 --- a/website/content/en/docs/Getting Started/future/developer-guide.md +++ b/website/content/en/docs/Getting Started/future/developer-guide.md @@ -77,7 +77,7 @@ Run e2e tests with minikube: ```bash make minikube-start eval $(minikube docker-env) -make build e2e config=config.minikube.env CR=podman +make build e2e config=config.minikube.env CONTAINER_RUNTIME=podman ``` `config.minikube.env` is the E2E test profile which provides all connection info to operator to run on minikube. @@ -85,7 +85,7 @@ make build e2e config=config.minikube.env CR=podman Run the specific e2e test: ```bash -make build e2e E2E_TEST_SELECTOR='^TestConfiguration$' config=config.minikube.env CR=podman +make build e2e E2E_TEST_SELECTOR='^TestConfiguration$' config=config.minikube.env CONTAINER_RUNTIME=podman ``` If you want to run E2E tests on CRC (Code Ready Containers by OpenShift), you should use `config.crc.env` profile instead of `config.minikube.env`.