7b73aa0c84
* ci(compute): use debian public image on the VM, not the container Previous behavior: We were pulling the debian image the wrong way, as this was being used as a container but it was meant to be the VM image The image being pulled to create the internal container has been causing crashes as this images do not exists on Google's container repositories Expected behavior: Use a public image as debian-11 to get multiple benefits from it, as being able to use machine-images (#5615) and automatic disk resizing (which is now possible as we're using COS images, but those are more restrictive) Solution Add `--image-project=debian-cloud` and `--image-family=debian-11` as stated in the official documentation: https://cloud.google.com/sdk/gcloud/reference/compute/instances/create-with-container#--image-project More info: https://cloud.google.com/compute/docs/images/os-details#import * fix: use a public image with docker on the host * fix(logs): missing sudo before docker command Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| PULL_REQUEST_TEMPLATE | ||
| workflows | ||
| CODEOWNERS | ||
| dependabot.yml | ||
| mergify.yml | ||
| pull_request_template.md | ||
| release-drafter.yml | ||
| zbot.yml | ||