Major Description
When running the APIcast container image it spawns a background process for dnsmasq.
This is difficult to support for a number of reasons.
Most importantly:
First, if the dnsmasq process exits then it doesn't stop the apicast process and the container will continue to run but it will encounter errors when it tries to resolve hosts. See attached screenshot.
Second, if there is an issue with dnsmasq it's difficult to diagnose. dnsmasq is run using --log-facility=- which means the syslog is output to stderr but since the process is run in daemon mode the logs don't appear to be reachable. If they are, please instruct on how retrieve them. Customers will be relying on relevant docker commands, oc commands, or the openshift console to retrieve the logs.
It's best practice to limit containers to a single process and not spawn background processes. If it is a technical requirement to run dnsmasq in the same container, we should manage the process better and react to dnsmasq process exits and make the logs easier to retrieve.
