Skip to content
This repository has been archived by the owner on Mar 29, 2022. It is now read-only.

Using docker local registry instead of quay.io for canary #8

Open
woohhan opened this issue Jun 9, 2020 · 2 comments
Open

Using docker local registry instead of quay.io for canary #8

woohhan opened this issue Jun 9, 2020 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@woohhan
Copy link
Contributor

woohhan commented Jun 9, 2020

For e2e testing, we're using quay.io for uploading canary(testing) image. This can cause problems that if someone runs multiple e2e tests at the same time. Instead of using quay.io, using docker local registry.

@woohhan woohhan added the bug Something isn't working label Jun 9, 2020
@woohhan woohhan assigned hyoung-90 and unassigned hbinkim Jun 16, 2020
@woohhan
Copy link
Contributor Author

woohhan commented Jun 16, 2020

Please take a look this issue @hyoung-90

@hyoung-90
Copy link
Collaborator

minikube drive=none

build)
  operator-sdk build kubevirt-image-service:canary
;;

minikube drive=docker, virtualbox

build)
  # shellcheck disable=SC2046
  eval $(minikube -p minikube docker-env)
  sleep 1
  operator-sdk build kubevirt-image-service:canary
  # shellcheck disable=SC2046
  eval $(minikube -p minikube docker-env -u)
;;
e2e) operator-sdk test local ./e2e --debug --verbose --image kubevirt-image-service:canary;;

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants