kubernetes-sigs/image-builder

WASM shims not working on Mariner image in Azure

mboersma opened this issue · 6 comments

mboersma commented

What steps did you take and what happened:

I deployed a Mariner Linux image using make build-azure-sig-mariner-2 and deployed a CAPZ cluster referencing it. After testing a few things, I tried testing WASM workloads and got an error, suggesting perhaps the configuration is incorrect for moby-containerd.

Sadly, I didn't retain the logs so I'll need to test this again to get the specific error (and fix).

What did you expect to happen:

WASM workloads should be scheduled just as they are on an Ubuntu image, since this feature should be enabled for all Azure builds.

Anything else you would like to add:

Environment:

Project (Image Builder for Cluster API:

Additional info for Image Builder for Cluster API related issues:

  • OS (e.g. from /etc/os-release, or cmd /c ver):
  • Packer Version:
  • Packer Provider:
  • Ansible Version:
  • Cluster-api version (if using):
  • Kubernetes version: (use kubectl version):

/kind bug

k8s-triage-robot commented

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

willie-yao commented

/remove-lifecycle stale
/priority backlog