Re: [go-nuts] Early hooking runtime - making libcontainer cross compilable

2017-02-17 Thread Ian Lance Taylor
On Fri, Feb 17, 2017 at 3:22 PM, Steven Hartland wrote: > > That said after fork we only have a single thread, so it should be possible > to perform these actions safely if it where possible to run arbitrary > actions via SysProcAttr and care was taken. We are never going to make it possible to r

Re: [go-nuts] Early hooking runtime - making libcontainer cross compilable

2017-02-17 Thread Steven Hartland
On 17/02/2017 22:36, Ian Lance Taylor wrote: On Fri, Feb 17, 2017 at 1:55 PM, Steven Hartland wrote: Recently we started adding support to our systems for opencontainers via libcontainer however due to its use of C code for the early hooking this means we now can't cross-compile our code any mo

Re: [go-nuts] Early hooking runtime - making libcontainer cross compilable

2017-02-17 Thread Ian Lance Taylor
On Fri, Feb 17, 2017 at 1:55 PM, Steven Hartland wrote: > Recently we started adding support to our systems for opencontainers via > libcontainer however due to its use of C code for the early hooking this > means we now can't cross-compile our code any more, which is a PITA. > > The main reason f

[go-nuts] Early hooking runtime - making libcontainer cross compilable

2017-02-17 Thread Steven Hartland
Recently we started adding support to our systems for opencontainers via libcontainer however due to its use of C code for the early hooking this means we now can't cross-compile our code any more, which is a PITA. The main reason for this is the early hooking required to perform setns as deta