[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic-devel] Friends don't let friends run Docker on loopback in production
- From: Jason Brooks <jbrooks redhat com>
- To: Colin Walters <walters verbum org>
- Cc: atomic-devel projectatomic io
- Subject: Re: [atomic-devel] Friends don't let friends run Docker on loopback in production
- Date: Wed, 15 Apr 2015 11:58:14 -0400 (EDT)
----- Original Message -----
> From: "Colin Walters" <walters verbum org>
> To: atomic-devel projectatomic io
> Sent: Wednesday, April 15, 2015 8:51:46 AM
> Subject: [atomic-devel] Friends don't let friends run Docker on loopback in production
>
> Hi,
>
> I've seen several people using Docker on loopback; this is the default if you
> use a mainline system + yum install Docker, as opposed to an Atomic host
> which uses https://github.com/projectatomic/fedora-productimg-atomic and
> https://github.com/projectatomic/docker-storage-setup
Is there a good guide out there for converting your mainline system + yum
install Docker installation to the preferred setup?
Jason
>
> I submitted this:
>
> https://github.com/docker/docker/pull/12404
>
> However, I think we can do more here.
>
> - Anaconda UI for reserving a thin pool
> - overlayfs
>
> I'm thinking of making this warning even stronger (as in it's emitted on the
> client, not just part of the intense amount of spam the docker daemon emits
> every time you run a container[1]).
>
> Any other thoughts?
>
> [1] And we really need to fix NM to not spew lots when Docker makes veth
> devices (https://bugzilla.gnome.org/show_bug.cgi?id=731014 ) etc
>
>
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]