feat: add a new shim for Wasm Workers Server

[Angelmmiguel]

Hello 👋

My name is Angel and I'm part of the Wasm Labs team. I'm a maintainer of the Wasm Workers Server project, an OSS project to develop and run serverless applications on top of WebAssembly.

I created a new shim that adds support for this kind of workloads. It allows you to run Wasm Workers Server apps the same way you can now with Spin and Slight. Here you have several example apps.

The code is pretty similar to the slight and spin shims. It was an easy integration thanks to all the features provided by runwasi and the previous work on those shims. Thank you for all your effort on this! 😄

I also updated the documentation and scripts to reflect the new shim.

Summary

• Introduce a new containerd-shim-wws-v1 shim
• Update build and testing scripts to cover it
• Test the changes in the CI
• Update documentation to information about the new shim

Please, feel free to suggest any change or requirement on the PR.

Thank you!

[Angelmmiguel]

@microsoft-github-policy-service agree company="VMware, Inc"

[squillace]

I'm really looking forward to this.

[Mossaka]

@Angelmmiguel thanks for your contribution! I am really excited for this. I will be travelling to attend KubeCon EU next week and will be back on April 23rd. Will review your PR by then.

[Angelmmiguel]

@Angelmmiguel thanks for your contribution! I am really excited for this. I will be travelling to attend KubeCon EU next week and will be back on April 23rd. Will review your PR by then.

That’s great @Mossaka! I’ll be in KubeCon too 😄

[Mossaka]

Will try to run this locally on my machine today and review the PR! Thanks for waiting

[Mossaka]

Mostly LGTM! I will need to run commands locally to test everything still works, and run CI to make sures it still works. Awesome work @Angelmmiguel !

I will ask @devigned to take another look.

[devigned]

Fantastic work, @Angelmmiguel! I have a couple questions.

[Mossaka]

I've tried make up and make test locally and it looks like all the images were able to built correctly and loaded correctly to k3d, but I was not able to get the response from wws shim, unlike the other shims.

I believe the issue was that the lable was not correctly set up

The pod had an error message in its events saying

Warning  FailedScheduling  16s   default-scheduler  0/2 nodes are available: 2 node(s) didn't match Pod's node affinity/selector. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.

[Mossaka]

Heyy I got the result!! That's awesome

The issue was described above: when I did make up, the wws-enabled=true label was not applied to the agent node. Once I added this label, the pod started normally and I was able to get this result.

[squillace]

whooohoooooo

[Angelmmiguel]

@Mossaka @devigned thank you for taking a look at the PR and for the complete testing! Agree with all your comments. I will fix the different issues and update the PR :)

[Angelmmiguel]

@Mossaka @devigned thank you for the thorough review! I already submitted some changes regarding using the 3000 port and the missing Makefile tasks and deps.

The pending changes are:

• Expose workers logs in the pod via stderr
• Ensure the make up command works correctly with the wws-shim

I'm having some issues regarding my environment (Docker Desktop on MacOS M1) when building the different shims. I get an error when compiling the openssl rust dependency as it tries to use the musl-ranlib binary instead of the x86_64-linux-musl-gcc-ranlib provided by the Cross base image. That's the reason I had to add all the environment variables to the Dockerfile for building wws. For now, I'm focusing on the wws-shim, but I may open a different issue and PR in the future to ensure the compilation works in the different environments.

Thank you!

[squillace]

If you wanna chat with @rumpl about Docker, he knows ALL :-)

[Angelmmiguel]

If you wanna chat with @rumpl about Docker, he knows ALL :-)

That would be really great! I think this case is a mix of Docker and Rust + Cross. It should a simple configuration thing. If you have some time @rumpl, it would be great to check it :)

Thank you for the introduction @squillace!

[Angelmmiguel]

@Mossaka @devigned the PR is ready for a second review when you have some time! 🎉

[Angelmmiguel]

I found this configuration option useful when working with MacOS M1. Now, I can configure the image to linux/arm64 when working with k3d. However, I can move this to a separate PR if it's more convenient

[devigned]

lgtm!

[Mossaka]

lgtm! Thanks for your contribution @Angelmmiguel