[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[atomic-devel] Q: Detecting Container-ness is still container=something?
- From: Chris Evich <cevich redhat com>
- To: atomic-devel projectatomic io
- Cc: bmr redhat com
- Subject: [atomic-devel] Q: Detecting Container-ness is still container=something?
- Date: Thu, 21 Jan 2016 10:41:18 -0500
All,
Looking for some advice re: a tooling bug. The problem (bug) has to do
with sosreport incorrectly determining whether or not it's not running
w/in a SPC container. The context is always going to be from within an
SPC, on an RHEL/Fedora/CentOS Atomic host. Sosreport needs to be useful
in helping diagnosing __host__ problems, with container data-collection
being a secondary use-case.
To address detection, we're aware of 'container=docker', and 'HOST', but
both seem quite flimsy. We've also considered a check based on
/proc/1/root. We also understand "container-ness" in some cases may be
intentionally obscured for security/isolation purposes.
For the general case (no security issue), in RHEL/Fedora/Centos Atomic
Host, within a SPC context, is checking the container env. var still the
preferred method?
Thanks in advance for any advice on this.
--
Chris Evich, RHCA, RHCE, RHCDS, RHCSS
Quality Assurance Engineer
Eeek! A BUG!!! -- Nooooo don't squash it!!! -- That's job-security!!!
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]