-
Notifications
You must be signed in to change notification settings - Fork 50
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
Refactor cross container and bump runwasi #162
Conversation
4867c67
to
1fd2964
Compare
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.
lgtm!
04a1abb
to
b908d78
Compare
rebased |
b908d78
to
ec4a8a3
Compare
8f7c94c
to
5a8cc73
Compare
It looks like enabling seccomp is messing with the CI tests. |
343fef5
to
de051f6
Compare
Signed-off-by: Jorge Prendes <jorge.prendes@gmail.com>
Signed-off-by: Jorge Prendes <jorge.prendes@gmail.com>
Signed-off-by: Jorge Prendes <jorge.prendes@gmail.com>
de051f6
to
746148b
Compare
It turns out it was a bug in upstream Everything should work fine with |
Thanks, @jprendes. Merging it now. |
This PR refactors and unifies the
Dockerfile
s used bycross-rs
for the different shims.As part of the refactor:
runwasi
is bumped to latest commitlibseccomp
is made available in the container, as it's not required byrunwasi
We also accidentally lost cgroups v1 support with #148. This PR re-enables it by bumping
runwasi
(which now enables it unconditionally).Note:
There are failures running the shims when seccomp is enabled.-> fixed by bumping runwasi to include youki's UB fix.