That error is pointing to a problem, the directory should be empty when
this isn't mounted, if it's got stuff, then that stuff is not actually
in the container rootfs.
On Thu, Apr 04, 2019 at 05:30:16PM -0400, Brandon Whaley wrote:
> Thank you for taking a look. I was able to rsync and confirm th
Thank you for taking a look. I was able to rsync and confirm that
everything worked as expected if I leave the instance running in
privileged mode during the rsync. I was wondering if you could
elaborate on the zfs mount option. When I try to mount it via `zfs
mount default/containers/instance-0
LXD only mounts the ZFS datasets when the container is started, so you should:
- Set security.privileged to true
- Start the container (or alternatively manually "zfs mount" it)
- Rsync
- Stop or unmount the container
- Unset security.privileged
- Start it
On Thu, Apr 04, 2019 at 10:42:38AM
All,
We have a native LXD server (3.0.0) and I was curious about upgrading to
3.11 via snap. I installed an 18.04 LTS server and then installed lxd via
snap (3.11). I copied a few containers over that I could easily stop on the
native server. Installing 18.04 LTS server installs a native copy of L
I'm in the middle of migrating some users from VZ to LXC/LXD with ZFS
backed guest fs. I'm using rsync with --numeric-ids to copy the files
with the correct uid/gid to the container's private area. It was
suggested to me that I could get the uid/gid remapping done by making
the destination contai
