Closed cpuguy83 closed 6 years ago
I have not yet setup the Makefile for root tests ala containerd.
LGTM on first pass.
Ah good, I need to find some time to work on this now...
For some reason we need sudo to run the fs tests. copy_file_range is getting EPERM otherwise.... could be related to a seccomp policy or something in the travis container config?
Ok, this is green.
LGTM, I think we should reorganize README to cover non-proto packages like this
Sudo doesnt affest seccomp policy so no...
On 25 Jan 2018 00:09, "Brian Goff" notifications@github.com wrote:
For some reason we need sudo to run the fs tests. copy_file_range is getting EPERM otherwise.... could be related to a seccomp policy or something in the travis container config?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/containerd/continuity/pull/101#issuecomment-360317104, or mute the thread https://github.com/notifications/unsubscribe-auth/AAdcPCzNiyUpmB3pSjBzGhSaiPtC9qnoks5tN8Y-gaJpZM4RqmbC .
@justincormack Well, when sudo
is used on travis you get a full VM rather than a container.
Ah. Well almost certainly then they are running a seccomp policy/docker version that is older than their kernel, so doesnt know about copy_file_range
and blocks it, while the kernel does support it..
Can you drop the github.com/containerd/containerd
files now that they are no longer needed. I see you already removed the errdefs requirement and removed from the vendor file.
Good catch, done.
This allows the fs package to be versioned separately from containerd and makes for a nice interface for filesystem interactions in continuity.