RFE: new release? #177
Comments
|
Yes, we are in the process of a v2.4.2 libseccomp release. I don't have a timeframe yet, but it should be in the next few weeks. Thanks! |
|
Since we're already tracking the release effort through milestones I think we can close this out. |
AkihiroSuda
added a commit
to AkihiroSuda/docker
that referenced
this issue
Dec 31, 2019
* Requires containerd binaries from containerd/containerd#3799 . Metrics are unimplemented yet. * Works with crun v0.10.4, but `--security-opt seccomp=unconfined` is needed unless using master version of libseccomp ( containers/crun#156, seccomp/libseccomp#177 ) * Doesn't work with master runc yet * Resource limitations are unimplemented Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
docker-jenkins
pushed a commit
to docker-archive/docker-ce
that referenced
this issue
Jan 9, 2020
* Requires containerd binaries from containerd/containerd#3799 . Metrics are unimplemented yet. * Works with crun v0.10.4, but `--security-opt seccomp=unconfined` is needed unless using master version of libseccomp ( containers/crun#156, seccomp/libseccomp#177 ) * Doesn't work with master runc yet * Resource limitations are unimplemented Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp> Upstream-commit: 612343618dd7dad7cf023e6263d693ab37507a92 Component: engine
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
the Docker default seccomp profile changed to include io_uring_* syscalls.
It doesn't work with the last released version of libseccomp since it lacks the definition for these syscalls.
The issue is already resolved on master, could it be possible to tag a new release?
The text was updated successfully, but these errors were encountered: