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
io-uring support #39396
Comments
|
This likely needs to be added to the seccomp profile here: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json Note you can provide your own seccomp profile to unblock yourself. You can also set the default profile as a daemon option:
|
Thanks so much ur comment points me to the right way. However the upstream hasn't included support for io-uring yet, but I already PRed it: seccomp/libseccomp#157 Plus there's a few typo: Currently I workaound the problem by just allow every system call to pass: But this config is highly unsafe under production circumstances. I think this could be put on hold until the upsteam gain uring support, then I could add it to the default config. |
|
for future visitors; these were removed again in; |
I'm currently using containers for my workzone, and I'm just getting my hands on the new io-uring thingy in kernel 5.1 here
And then I noticed that docker currently blocks the io-uring related requests :
While this test program runs without a problem on the host machine (I'm using a fedora30 host with docker-machine --drive generic)
So I thought this would be the place to suggest this feature
The text was updated successfully, but these errors were encountered: