Akihiro Suda

Needs rebase

@kolyshkin ptal

Looks like we will have to add a few arch-specific constants to support ppc64le, s390x, arm (32-bit), and other minor architectures.

I don't like the mega dependency on `gvisor.dev/gvisor/pkg/*`. https://github.com/google/gvisor/blob/e0e9a19bffcb4fd4e545d3942104734f4d911f92/pkg/seccomp/seccomp_unsafe.go#L23 https://github.com/google/gvisor/blob/e0e9a19bffcb4fd4e545d3942104734f4d911f92/pkg/abi/linux/linux_amd64_abi_autogen_unsafe.go#L15-L17 Probably, we should fork `gvisor.dev/gvisor/pkg/seccomp` and its minimum dependency to another repo. (`opencontainers/go-seccomp`? `moby/sys/seccomp`? Or just `opencontainers/runc/libcontainer/seccomp`?)

> This is my simple interest, what is the reason you want to change the seccomp library? Are there any hard spots? Cross-compilation is often cumbersome with cgo. Also, distros'...

Removed from v1.2.0 milestone, but contribution is still welcome

@utam0k Assigned

@utam0k Thank you for taking a look at this. I think it is ok to fork the repo for implementing the missing features. Forking seems also almost necessary to get...

Better to move to v1.1.0 milestone?

Can we have integration test (in this repo)?