Hello,
$ dpkg -l | grep lxc
ii liblxc1
1.1.5-0ubuntu0.15.10.3 amd64 Linux Containers
userspace tools (library)
ii lxc
1.1.5-0ubuntu0.15.10.3 amd64 Linux Containers
userspace tools
ii lxc-templates
1.1.5-0ubuntu0.15.10.3 amd64 Linux Containers
userspace tools (templates)
ii lxcfs 0.10-0ubuntu2.1
amd64 FUSE based filesystem for LXC
ii python3-lxc
1.1.5-0ubuntu0.15.10.3 amd64 Linux Containers
userspace tools (Python 3.x bindings)
yesterday I needed to play with Moodle so I made a snapshot from another
container I had.
$ sudo lxc-stop -n moodle
$ sudo lxc-clone -s moodle moodle30
$ sudo lxc-start -dn moodle30
I updated Moodle in the new container. Made some tests. And stoped the
container.
Today, I restarted the container (moodle30) and ls -l showed some weird
files, so I stoped the container.
ls -l /var/lib/lxc/moodle30/delta0/home/ubuntu/moodle shows:
-rw-rw-r-- 1 sysadmin sysadmin 42250 mar 8 01:36 config-dist.php
-rw-r--r-- 1 sysadmin sysadmin 691 mar 8 01:35 config.php
c--------- 1 root root 0, 0 mar 8 01:35 config.php~
Note config.php~
Now, after starting the container again, ls (inside the container) doesn't
show those 'c' files.
Backend FS is ext4
Is this a know bug of -s with ext4 backend? Is there any way to avoid it
(going to lvm/btrfs/zfs is not an option right now but I can accept it for
future deployments).
Thanks!
Norberto
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users