Skip to content

Conversation

Signed-off-by: Tonis Tiigi <[email protected]>
(cherry picked from commit c38341f)
@thaJeztah
Copy link
Member

I guess it should be possible to switch back to "upstream" once moby/moby#42836 is merged into the 20.10 branch?

@aojea
Copy link

aojea commented Sep 28, 2021

I guess it should be possible to switch back to "upstream" once moby/moby#42836 is merged into the 20.10 branch?

let me use the opportunity to ask 😄 , what is the ETA for the backport @thaJeztah ?

@thaJeztah
Copy link
Member

soontm, hopefully

@tonistiigi
Copy link
Member Author

I guess it should be possible to switch back to "upstream" once moby/moby#42836 is merged into the 20.10 branch?

Depends on how big the diff is

@tonistiigi tonistiigi merged commit e3ef32f into moby:v0.9 Sep 28, 2021
flokli added a commit to wireapp/wire-server that referenced this pull request Jun 8, 2022
glibc 2.34 uses the clone3 syscall, which is not part of the seccomp
filters that moby ships on older versions.

While as a workaround you might be able to run containers with
`--privileged`, it's the better call to just run a more recent Docker
runtime.

References:
 - docker/buildx#772
 - moby/buildkit#2379
 - moby/moby#42836
 - NixOS/nixpkgs#170900
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants