-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add LinuxContainerExecutor
to Wasmtime and WasmEdge shims
#156
Conversation
We may need to revisit this since #147 would mean the wasm binary would definitely not be in the rootfs |
4ff9d3c
to
c9dee9f
Compare
7cb3119
to
30456c3
Compare
This commit implements can_handle in wasmtime executor. It checks if the entrypoint binary has wasm as the path extension. If not, the wasmtime executor will not be used. It adds a default executor to the wasmtime shim as a backup so it enables running wasm and containers side-by-side. Add wat extension support in can_handle Signed-off-by: jiaxiao zhou <jiazho@microsoft.com>
this commit adds a python container in the test directory. It also adds a few commands in the makefile to build the python flask app into a container, load into the kind cluster for testing. Eventually the wasmtime tests will have both python container and a wasm contaienr running in a pod. Signed-off-by: jiaxiao zhou <jiazho@microsoft.com>
Signed-off-by: jiaxiao zhou <jiazho@microsoft.com>
The issue says "WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load" Signed-off-by: jiaxiao zhou <jiazho@microsoft.com>
Could I please have some review comments on this PR? 🙏🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just one suggestion. otherwise LGTM
Signed-off-by: jiaxiao zhou <jiazho@microsoft.com>
Signed-off-by: jiaxiao zhou <jiazho@microsoft.com>
Looking through youki a bit, I think |
Yeah, as @0xE282B0 mentioned, this was the latest breaking change post |
Signed-off-by: jiaxiao zhou <jiazho@microsoft.com>
I've updated this PR to add linux container executors to both Wasmtime and WasmEdge shims. |
LinuxContainerExecutor
to Wasmtime and WasmEdge shims
this commits adds the default executor to the wasmedge shim similar to how wasmtime shim gets it. It made an API change to the containerd-shim-wasm crate by moving default executor logic from wasmtime shim upstream for sharing code. Signed-off-by: jiaxiao zhou <jiazho@microsoft.com>
Hey thanks everyone for reviewing this PR! 🙌🥂 I realized it's very difficult to squash commits before merge so I did a squash merge all together to make main branch clean. We can set a policy to only allow squash merge, wdyt? @jsturtevant |
Signed-off-by: James Sturtevant <jstur@microsoft.com>
Signed-off-by: James Sturtevant <jstur@microsoft.com>
Signed-off-by: James Sturtevant <jstur@microsoft.com>
Signed-off-by: James Sturtevant <jstur@microsoft.com>
This PR adds a
LinuxContainerExecutor
to both the Wasmtime and Wasmedge shims. It enables the shims to be able to execute containers side by side with wasms.Some notable changes
libcontainer_instance
module tocontainerd-shim-wasm
which provides a linux container executor implementation that is shared by both wasmtime and wasmedge shims.