sampointer/kapo

Wrap any command in a status socket

About Me

I've been putting and keeping things on the Internet for 20 years, including back-end game infrastructure on various and varied platforms, and a prominent consumer IoT platform, amongst others.

The first software I ever released was Shareware for the ATARI ST. The first job I ever had was writing IBM S/390 Assembler. Since then I've been through C, Perl, Ruby. Today I mainly write Go.

I'm an SRE. I write software to automate the provisioning and maintenance of Cloud Infrastructure. In general, that's the easy bit.

If you've read this far then I can trust you enough to tell you I'm also the original author of runson.cloud, although that project has long since been taken over by other maintainers.

kapo's Issues

STDOUT/STDERR pass-through for wrapped command

First of all, thank you for releasing kapo. It matches perfectly the use case of remotely health checking applications/containers of non-network based apps.

We intent to use it for some Sidekiq dedicated containers but we couldn't find a way to keep sidekiq's original stdout/stderr logging. The moment container starts, its logging is suppressed by kapo. Just an excerpt from docker-compose logs sidekiq:

...
sidekiq_1        | Bundled gems are installed into /usr/local/bundle.
sidekiq_1        | INFO[0000] binding to 0.0.0.0:6666                      
sidekiq_1        | INFO[0000] running /usr/local/bin/bundle exec sidekiq   

When we run sidekiq without kapo, we have all stdout/stderr passed to docker logs successfully:

...
sidekiq_1        | Bundled gems are installed into /usr/local/bundle.
sidekiq_1        | 2017-06-28T12:13:39.102Z 51 TID-7bn68 INFO: Booting Sidekiq 5.0.0 with redis options {:url=>"redis://redis:6379/2"}
sidekiq_1        | 
sidekiq_1        | 
sidekiq_1        |          m,
sidekiq_1        |          `$b
sidekiq_1        |     .ss,  $$:         .,d$
sidekiq_1        |     `$$P,d$P'    .,md$P"'
sidekiq_1        |      ,$$$$$bmmd$$$P^'
sidekiq_1        |    .d$$$$$$$$$$P'
sidekiq_1        |    $$^' `"^$$$'       ____  _     _      _    _
sidekiq_1        |    $:     ,$$:       / ___|(_) __| | ___| | _(_) __ _
sidekiq_1        |    `b     :$$        \___ \| |/ _` |/ _ \ |/ / |/ _` |
sidekiq_1        |           $$:         ___) | | (_| |  __/   <| | (_| |
sidekiq_1        |           $$         |____/|_|\__,_|\___|_|\_\_|\__, |
sidekiq_1        |         .d$$                                       |_|
sidekiq_1        | 
sidekiq_1        | 2017-06-28T12:13:39.291Z 51 TID-7bn68 INFO: Running in ruby 2.3.4p301 (2017-03-30 revision 58214) [x86_64-linux]
sidekiq_1        | 2017-06-28T12:13:39.291Z 51 TID-7bn68 INFO: See LICENSE and the LGPL-3.0 for licensing details.
sidekiq_1        | 2017-06-28T12:13:39.291Z 51 TID-7bn68 INFO: Upgrade to Sidekiq Pro for more features and support: http://sidekiq.org
...

Does kapo have any runtime option enabling stdout/stderr passthrough or is this something out of scope?