Package: lxc
Version: 0.9.0~alpha3-2
Severity: important
File: /usr/bin/lxc-clone
Dear Maintainer,
* What led up to the situation?
Attempted to use lxc-clone to clone a container
* What exactly did you do (or not do) that was effective (or
ineffective)?
lxc-clone -o uwsgi1 -n uwsgi2
or even
lxc-clone -o uwsgi1 -n uwsgi2 -v VmStorage
or even
lxc-clone -o uwsgi1 -n uwsgi3 -v VmStorage -t xfs
* What was the outcome of this action?
a cloned container as it would do with a directory backed container
* What outcome did you expect instead?
here is the output
root@batou:~# lxc-clone -o uwsgi1 -n uwsgi3 -v VmStorage -t xfs
Tweaking configuration
Copying rootfs...
Logical volume "uwsgi3_snapshot" created
UUID = cd8c7fbf-04c2-4eda-81da-408e80dd0180
Clearing log and setting UUID
writing all SBs
new UUID = 58c0b2f7-24fb-418a-a7b2-af3328b9ce38
mkdir: cannot create directory ‘/dev/VmStorage/uwsgi3_snapshot’: File
exists
root@batou:~#
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lxc depends on:
ii debconf [debconf-2.0] 1.5.50
ii libapparmor1 2.8.0-1
ii libc6 2.17-7
ii libcap2 1:2.22-1.2
ii multiarch-support 2.17-7
Versions of packages lxc recommends:
ii debootstrap 1.0.53
ii libcap2-bin 1:2.22-1.2
Versions of packages lxc suggests:
pn debian-keyring <none>
ii gpgv 1.4.12-7
ii live-debconfig-doc 4.0~a25-1
ii rsync 3.0.9-4
-- debconf information:
lxc/shutdown: /usr/bin/lxc-halt
lxc/directory: /var/lib/lxc
lxc/title:
lxc/auto: true
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
