On Wed, Feb 14, 2018, at 10:45 AM, James Thomas wrote:
> Michele,
>
> Great work on getting an implemention working so quickly... I've been
> playing with it locally and it works perfectly.
Yes. It is actually in the state where I can run some performance tests.
That is my next step. I want to
- on notifying the caller of a failed exec: logs should be available even if
container fails between init and run. As long as the logs appear on stdout and
stderr they are fetched and amended to the activation record. This would appear
as a generic error message that’s system generated and
Michele,
Great work on getting an implemention working so quickly... I've been
playing with it locally and it works perfectly. I have a couple of
questions about the error handling and exec process.
1. Notifying user when exec fails?
Looking at the code, the exec to replace the binary happens
As promised I released a first implementation of Go support using the technique
I described before.
In short, a library implementing the proxy and serving both /run and /init,
with the ability of replace itself with a new version.
Using the library, implementing a function in Go looks like
