Receiving panic when trying to run hologram-agent in a Kubernetes pod

[ecottd]

I am attempting to leverage hologram from within a K8s pod to help manage AWS credentials. This has worked in a prior system we use. We are moving to a terraform based build of the pods and this is resulting in errors running the hologram agent.

When trying to run the agent without any extra arguments, I get the following.

panic: runtime error: invalid memory address or nil pointer dereference[signal
SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x56344d]

goroutine 1 [running]:
log/syslog.(*Writer).writeAndRetry(0x0, 0x28?,{0xc0000dc870,0x28})
/usr/local/go/src/log/syslog/syslog.go:251+0x4d
log/syslog.(*Writer).Info(...)
/usr/local/go/src/log/syslog/syslog.go:239
github.com/AdRoll/hologram/log.(*syslogSink).Info(0xa8130a?,{0xc0000dc870?,0xc00019ff38?})
/go/src/github.com/AdRoll/hologram/log/syslog.go:39+0x2c
github.com/AdRoll/hologram/log.(*logMux).Info(0xc0000c6060,{0xa8130a?,0x7f7f605ce5b8?},{0xc00019ff38?,0x10b5c60?,0xc00009e690?})
/go/src/github.com/AdRoll/hologram/log/mux.go:50+0xa8github.com/AdRoll/hologram/log.Info({0xa8130a?,0x1?},{0xc00019ff38?,0x9ac7a0?,0x10b4dc0?})
/go/src/github.com/AdRoll/hologram/log/log.go:79+0x12dmain.main()
/go/src/github.com/AdRoll/hologram/cmd/hologram-agent/main.go:98+0x445

It looks like the Go logger is failing to instantiate.

Any ideas as to why this might be?