** No longer affects: lxc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293549
Title:
Filesystem mount from lxc template causes filesystem permission
breakages
To manage notifications about
** Changed in: postgresql (Juju Charms Collection)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293549
Title:
Filesystem mount from lxc template causes filesystem
** Changed in: juju-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293549
Title:
Filesystem mount from lxc template causes filesystem permission
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293549
Title:
Filesystem mount from lxc template causes filesystem permission
A naieve test of aufs directly shows that chown and chmod do cause a
copy up of the underlying files as expected.
In the read only layer before chmod/chown:
drwxrwxr-x 2 apw apw 4096 Mar 18 09:16 D1
drwxrwxr-x 2 apw apw 4096 Mar 18 09:16 D2
drwxrwxr-x 2 apw apw 4096 Mar 18 09:16 D3
In the
Ok a more refined reproducer shows that this is an issue triggered by
different permissions on the various layers. Although the directory is
reported correctly the permissions for each layer are used on that layer
to control who can actually see the contents of the directory. If you
cannot rx
Thanks, that is a great reproducer.
Note that doing
rm -rf /etc/ssl/private
mkdir /etc/ssl/private
works around this, and explains why this *may* in fact be on purpose. If you
only do
sudo chown ubuntu:ubuntu /etc/ssl/private
then the underlying directory is still owned by root and
@Tim,
is rmdir/mkdir an acceptable workaround for juju (ie can we lower
priority of the bug) or will that not be doable?
** Changed in: lxc
Status: New = Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided
17:07 infinity hallyn: Well, that certainly shouldn't change the permissions
on the underlying dir, as that's immutable.
17:07 infinity hallyn: But copying up, changing permissions, and using that
copy would seem sane.
--
You received this bug notification because you are a member of Ubuntu
@Serge, while it may be a work around for some, it certainly is going to
be a problem in the big picture.
We are running code written by others (juju hooks).
I'm going to submit a branch to juju to disable aufs by default, but
enable the setting so people can try it out.
** Branch linked:
or a chown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293549
Title:
Filesystem mount from lxc template causes filesystem permission
breakages
To manage notifications about this bug go to:
Shouldn't aufs catch a chmod to a directory that isn't in the delta and
copy it across?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293549
Title:
Filesystem mount from lxc template causes
12 matches
Mail list logo
