Also encountering what I consider a bug.
[inside lxc instance] /root # touch in
[OUTSIDE] # ls -la /var/lib/lxc/overlay/rw/root/in
-rw-r--r--. 1 root root0 May 31 22:12 /var/lib/lxc/overlay/rw/root/in
[inside lxc instance] # rm -f in
[OUTSIDE] # ls -la /var/lib/lxc/overlay/rw/root/in
... No
If it's only keep the files separate, then overlayfs should do the job.
Note that due to the nature of overlayfs, I wouldn't recommend RELYING
on packages upgraded on the host to be available on the container.
During your container customization, it's possible that you broke the
link (e.g.
On Sun, May 31, 2015 at 6:58 AM, james harvey jamespharve...@gmail.com wrote:
I want to create a container that starts out being identical to my
top-level no-container installation. I want any changes performed
within the container to be kept in the container. I want anything
added to my
I want to create a container that starts out being identical to my
top-level no-container installation. I want any changes performed
within the container to be kept in the container. I want anything
added to my top-level no-container installation to automatically show
up in already made
On Sat, May 30, 2015 at 8:29 PM, Fajar A. Nugraha l...@fajar.net wrote:
On Sun, May 31, 2015 at 6:58 AM, james harvey jamespharve...@gmail.com
wrote:
I want to create a container that starts out being identical to my
top-level no-container installation. I want any changes performed
within
What is your primary goal?
... Part of me is wondering if I can overlayfs everything, and chroot
a terminal into the overlayfs mount. Not too worried about malicious
apps for my situation in Linux. Just want to keep the files separate.
___
lxc-users
On Sun, May 31, 2015 at 8:14 AM, james harvey jamespharve...@gmail.com wrote:
What is your primary goal?
... Part of me is wondering if I can overlayfs everything, and chroot
a terminal into the overlayfs mount. Not too worried about malicious
apps for my situation in Linux. Just want to
