On Wed, Dec 9, 2015 at 10:06 PM, Dusty Mabe <dusty(a)dustymabe.com> wrote:
On 12/09/2015 11:52 PM, Chris Murphy wrote:
> On Wed, Dec 9, 2015 at 7:53 PM, Dusty Mabe <dusty(a)dustymabe.com> wrote: >
> >> You can populate /etc/sysconfig/docker-storage-setup and have it do what
> you >> want. The thing about it is that it isn't the smartest script and
if
> you >> don't tell it exactly what you want it to do, it can go off the
rails
> >> pretty easily (especially for a storage setup it isn't used to seeing).
> >> >> man docker-storage-setup will show you want you can put in the
file. >
> > Yeah this doesn't work for me either, I still get an error. I included >
> it in the bug below. > >> I'm guessing for your setup
docker-storage-setup
> is getting confused >> and things sda2 is a VG and tries to do something
> with that.. >> Probably a bug that needs to be filed. > >
>
https://bugzilla.redhat.com/show_bug.cgi?id=1290283
Since LVM isn't used docker-storage-setup looks like it is just
exiting out and not doing anything (but the messages from the logs
don't clearly indicate what is happening). A question is: what does
your system storage look like before docker-storage-setup runs and
what do you want it to look like after?
If I know that info maybe I can help you get there.
I was just trying to resolve the confusing error message. But even
after satisfying it by creating a thin pool, I still get the same
"sda2" error message. I've updated the bug.
Until the docker patch mentioned at the tail end of this bug lands, it
seems a bit of a hassle to use Btrfs as backing.
https://github.com/docker/docker/issues/7952
--
Chris Murphy