Sebastiaan van Stijn df650a1aeb panic() instead of logrus.Fatal() in init funcs ... Some packages were using `logrus.Fatal()` in init functions (which logs the error, and (by default) calls `os.Exit(1)` after logging). Given that logrus formatting and outputs have not yet been configured during the initialization stage, it does not provide much benefits over a plain `panic()`. This patch replaces some instances of `logrus.Fatal()` with `panic()`, which has the added benefits of not introducing logrus as a dependency in some of these packages, and also produces a stacktrace, which could help locating the problem in the unlikely event an `init()` fails. Before this change, an error would look like: $ dockerd FATA[0000] something bad happened After this change, the same error looks like: $ dockerd panic: something bad happened goroutine 1 [running]: github.com/docker/docker/daemon/logger/awslogs.init.0() /go/src/github.com/docker/docker/daemon/logger/awslogs/cloudwatchlogs.go:128 +0x89 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>		2022-04-21 12:15:20 +02:00
..
gcplogging.go	panic() instead of logrus.Fatal() in init funcs	2022-04-21 12:15:20 +02:00
gcplogging_linux.go	homedir: remove idtools and libcontainer's user package dependencies	2019-09-24 00:32:13 +00:00
gcplogging_others.go	Update to Go 1.17.0, and gofmt with Go 1.17	2021-08-24 23:33:27 +02:00