containerd/runtime
Erik Sipsma 48f46516ad Support disabling default setup of shim logger.
Before this change, the v2 runtime shim setup code was hardcoded to always
configure logrus to write logs to the "log" FIFO present in the current working
directory. This only happens in the "default" action codepath
(i.e. not shim start or shim delete).

This is problematic for shims that execute outside the current working
directory of a bundle. For example, it often doesn't make sense for shims that
manage multiple containers to execute in a single bundle directory. Additionally,
shim processes that require being pre-created, i.e. spun up before tasks they
will handle are actually created, won't have a log FIFO to write to until a task
is created.

This change leaves the default behavior as is but introduces a Binary Config
field that will optionally disable automatic configuration of logrus to use the
"log" FIFO. This allows shims to configure their own logger if necessary while
still re-using the rest of the shim helper code in containerd.

Signed-off-by: Erik Sipsma <sipsma@amazon.com>
2019-04-24 19:01:12 +00:00
..
linux/runctypes Regenerate protobufs 2019-04-03 23:41:15 +02:00
proc Shim pluggable logging 2019-03-12 12:18:28 -04:00
restart Cleanup workdirs on manager load 2018-07-30 10:21:04 -04:00
v1 Check task list to avoid unnecessary cleanup. 2019-04-11 16:29:09 -07:00
v2 Support disabling default setup of shim logger. 2019-04-24 19:01:12 +00:00
events.go Licence header added 2018-02-19 10:32:26 +09:00
monitor.go Licence header added 2018-02-19 10:32:26 +09:00
runtime.go runtime: add Add/Delete method in PlatformRuntime interface 2018-12-29 13:56:38 +08:00
task_list.go Runtime v2 2018-07-17 10:21:29 -04:00
task.go Runtime v2 2018-07-17 10:21:29 -04:00
typeurl.go Licence header added 2018-02-19 10:32:26 +09:00