Re: [atomic-devel] catch-22: diagnostic tools on Atomic Host

2016-06-28 Thread Daniel J Walsh
On 06/26/2016 05:39 PM, Joe Brockmeier wrote: On Fri, Jun 24, 2016 at 3:56 PM, Daniel J Walsh wrote: Well if you have the software already installed in containers you could always use atomic mount to mount a container image and then mount the host into the container and

Re: [atomic-devel] catch-22: diagnostic tools on Atomic Host

2016-06-26 Thread Joe Brockmeier
On Fri, Jun 24, 2016 at 3:56 PM, Daniel J Walsh wrote: >> > Well if you have the software already installed in containers you could > always use atomic mount to mount a container > image and then mount the host into the container and chroot into it. :^) Should we document

Re: [atomic-devel] catch-22: diagnostic tools on Atomic Host

2016-06-24 Thread Josh Berkus
On 06/24/2016 11:13 AM, Jonathan Lebon wrote: >> I'm not sure what the answer to this is; I'm reluctant to recommend >> installing a whole suite of diagnostic tools just for the case of a >> bare-metal user who has a problem. But on the other hand, the current >> situation isn't really vialble

Re: [atomic-devel] catch-22: diagnostic tools on Atomic Host

2016-06-24 Thread Jonathan Lebon
> I'm not sure what the answer to this is; I'm reluctant to recommend > installing a whole suite of diagnostic tools just for the case of a > bare-metal user who has a problem. But on the other hand, the current > situation isn't really vialble for bare-metal users either. There is now `ostree

[atomic-devel] catch-22: diagnostic tools on Atomic Host

2016-06-24 Thread Josh Berkus
Folks, In my bare metal testing, I've found a few issues. One of them is that AH doesn't ship with a lot of diagnostic tools. The general prescription is to install them via containers. However, if the problem you're having prevents docker from starting, then you're kind of stuck. In my case,