On mån, 2015-02-02 at 12:12 +0100, Lennart Poettering wrote:
> On Fri, 30.01.15 11:02, Alexander Larsson (al...@redhat.com) wrote:
>
> > I think the problem is that docker daemon makes
> > /var/lib/docker/devicemapper private in the host namespace to handle
> > some scalability issues we found in
On Fri, 30.01.15 11:02, Alexander Larsson (al...@redhat.com) wrote:
> I think the problem is that docker daemon makes
> /var/lib/docker/devicemapper private in the host namespace to handle
> some scalability issues we found in the kernel. This causes problem not
> with docker containers (because
On fre, 2015-01-23 at 11:31 -0500, Daniel J Walsh wrote:
> On 01/22/2015 10:02 PM, Lennart Poettering wrote:
> > On Sat, 17.01.15 23:02, Lars Kellogg-Stedman (l...@redhat.com) wrote:
> >
> >> See the `devicemapper` mountpoint created by Docker for the container:
> >>
> >> # grep devicemapper/mn
Yes I was trying to get a comment from Alex, since he did the original
patch.
On 01/23/2015 12:26 PM, Lennart Poettering wrote:
> On Fri, 23.01.15 11:31, Daniel J Walsh (dwa...@redhat.com) wrote:
>
> You just sent a full quote without any comment of yours?
>
>> On 01/22/2015 10:02 PM, Lennart Poet
On Fri, 23.01.15 11:31, Daniel J Walsh (dwa...@redhat.com) wrote:
You just sent a full quote without any comment of yours?
>
> On 01/22/2015 10:02 PM, Lennart Poettering wrote:
> > On Sat, 17.01.15 23:02, Lars Kellogg-Stedman (l...@redhat.com) wrote:
> >
> >> See the `devicemapper` mountpoint cr
On 01/22/2015 10:02 PM, Lennart Poettering wrote:
> On Sat, 17.01.15 23:02, Lars Kellogg-Stedman (l...@redhat.com) wrote:
>
>> See the `devicemapper` mountpoint created by Docker for the container:
>>
>> # grep devicemapper/mnt /proc/mounts
>>
>> /dev/mapper/docker-253:6-98310-e68df3f45d6
On Sat, 17.01.15 23:02, Lars Kellogg-Stedman (l...@redhat.com) wrote:
> See the `devicemapper` mountpoint created by Docker for the container:
>
> # grep devicemapper/mnt /proc/mounts
>
> /dev/mapper/docker-253:6-98310-e68df3f45d6151259ce84a0e467a3117840084e99ef3bbc654b33f08d2d6dd62
>
On Sun, 18.01.15 20:50, Colin Walters (walt...@verbum.org) wrote:
> On Sat, Jan 17, 2015, at 11:02 PM, Lars Kellogg-Stedman wrote:
> > Hello all,
> >
> > With systemd 216 on Fedora 21 (kernel 3.17.8), I have run into an odd
> > behavior concerning the PrivateTmp directive, and I am looking for
>
On Mon, Jan 19, 2015 at 08:54:52PM +0300, Andrei Borzenkov wrote:
> > What is causing this behavior? I have tried to replicate it by hand through
> > a
> > combination of mount and unshare, and the only way I can get a mount to
> > persist
> > in the unshare namespace after being unmounted in the
В Mon, 19 Jan 2015 11:33:42 -0500
Lars Kellogg-Stedman пишет:
> On Sat, Jan 17, 2015 at 11:02:01PM -0500, Lars Kellogg-Stedman wrote:
> > The TL;DR is that restarting a service with PrivateTmp=true appears to
> > preserve references to any mounts in the parent mount namespace that
> > were active
On Sat, Jan 17, 2015 at 11:02:01PM -0500, Lars Kellogg-Stedman wrote:
> The TL;DR is that restarting a service with PrivateTmp=true appears to
> preserve references to any mounts in the parent mount namespace that
> were active at the time the service was started. If these mounts are
> later unmou
On 19/01/15 08:39 -0500, Daniel J Walsh wrote:
On 01/19/2015 12:27 AM, Lars Kellogg-Stedman wrote:
On Sun, Jan 18, 2015 at 11:38:12PM -0500, Lars Kellogg-Stedman wrote:
I think we actually want MountFlags=slave, which will permit mounts
from the global namespace to propagate into the service n
On 01/19/2015 12:27 AM, Lars Kellogg-Stedman wrote:
> On Sun, Jan 18, 2015 at 11:38:12PM -0500, Lars Kellogg-Stedman wrote:
>> I think we actually want MountFlags=slave, which will permit mounts
>> from the global namespace to propagate into the service namespace
>> without permitting propagation
On Sun, Jan 18, 2015 at 11:38:12PM -0500, Lars Kellogg-Stedman wrote:
> I think we actually want MountFlags=slave, which will permit mounts
> from the global namespace to propagate into the service namespace
> without permitting propagation in the other direction. It seems like
> this would the Le
On Sun, Jan 18, 2015 at 11:38:12PM -0500, Lars Kellogg-Stedman wrote:
> On Sun, Jan 18, 2015 at 08:50:35PM -0500, Colin Walters wrote:
> > On Sat, Jan 17, 2015, at 11:02 PM, Lars Kellogg-Stedman wrote:
> > > Hello all,
> > >
> > > With systemd 216 on Fedora 21 (kernel 3.17.8), I have run into an o
On Sun, Jan 18, 2015 at 08:50:35PM -0500, Colin Walters wrote:
> On Sat, Jan 17, 2015, at 11:02 PM, Lars Kellogg-Stedman wrote:
> > Hello all,
> >
> > With systemd 216 on Fedora 21 (kernel 3.17.8), I have run into an odd
> > behavior concerning the PrivateTmp directive, and I am looking for
> > he
On Sat, Jan 17, 2015, at 11:02 PM, Lars Kellogg-Stedman wrote:
> Hello all,
>
> With systemd 216 on Fedora 21 (kernel 3.17.8), I have run into an odd
> behavior concerning the PrivateTmp directive, and I am looking for
> help identifying this as:
>
> - Everything Is Working As Designed, Citizen
>
Hello all,
With systemd 216 on Fedora 21 (kernel 3.17.8), I have run into an odd
behavior concerning the PrivateTmp directive, and I am looking for
help identifying this as:
- Everything Is Working As Designed, Citizen
- A bug in Docker (some mount flag is being set incorrectly?)
- A bug in syste
18 matches
Mail list logo
