Fix image build failed for GAR

[iQQBot]

Description

Fix image build failed for GAR

Related Issue(s)

Fixes CLC-1099

How to test

1. create a dummy repo, and use image from https://hub.docker.com/r/gitpod/workspace-base/tags (You can choose an image that has never been used before. The key point here is that you need to re-trigger the image build function and upload at least one blob file)
2. try start workspace from that repo in different preview env, make sure it failed.
3. try start workspace from that repo with this preview env, it will start image build and it should success

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - pd-clc-1099
• 🔗 URL - pd-clc-1099.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - pd-CLC-1099-gha.31367
• 🗒️ Logs - GCP Logs Explorer

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft preemptible
  Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[geropl]

@iQQBot Nice work, thanks for the super quick fix! 💪 Please ping once you have a preview running for testing 🙏

[iQQBot]

@geropl preview env is ready, and update how to test section

[iQQBot]

If you see 502, you can manually trigger gcp refresh token jobs

kubectl create job --from=cronjob/gcr-refresh-token gcr-refresh-token-manual

and restart image-builder-mk3, it's another problem. and it only happen in preview env

[geropl]

Nice, works! ✔️

[geropl]

Tested and works! 🎉 ✔️

[iQQBot]

/unhold