Quoting zoolook (nbensa+lxcus...@gmail.com):
LXC version: 0.9.0.0~staging~20130708-2041-0ubuntu1~ppa1~raring1
Hello,
there's an inconsistency between lxc-create --fssize and lxc-clone -L.
lxc-create --fssize accepts size in GB. For example, --fssize 2G
mease 2GB (or 2GiB, my brain
lxc-clone -L accepts size _only_ in B. In other words, ignores G.
Yup. You can see the local functions for parsing the fssize in
lxc_clone.c and lxc_create.c. Patch to commonize and improve them
would be very welcome.
Thanks. I'll take a look when I get back home.
LXC version: 0.9.0.0~staging~20130708-2041-0ubuntu1~ppa1~raring1
Hello,
there's an inconsistency between lxc-create --fssize and lxc-clone -L.
lxc-create --fssize accepts size in GB. For example, --fssize 2G
mease 2GB (or 2GiB, my brain hurts with all that GB vs GiB stupidity
but that's
Quoting zoolook (nbensa+lxcus...@gmail.com):
Hi Serge,
On Tue, Jun 18, 2013 at 5:57 PM, zoolook nbensa+lxcus...@gmail.com wrote:
On Tue, Jun 18, 2013 at 5:39 PM, Serge Hallyn serge.hal...@ubuntu.com
wrote:
Exactly what code (git commit id or distro+pkg) are you using?
Installed:
Quoting Serge Hallyn (serge.hal...@ubuntu.com):
Quoting zoolook (nbensa+lxcus...@gmail.com):
Hi Serge,
On Tue, Jun 18, 2013 at 5:57 PM, zoolook nbensa+lxcus...@gmail.com wrote:
On Tue, Jun 18, 2013 at 5:39 PM, Serge Hallyn serge.hal...@ubuntu.com
wrote:
Exactly what code (git
Quoting Serge Hallyn (serge.hal...@ubuntu.com):
Quoting Serge Hallyn (serge.hal...@ubuntu.com):
Quoting zoolook (nbensa+lxcus...@gmail.com):
Hi Serge,
On Tue, Jun 18, 2013 at 5:57 PM, zoolook nbensa+lxcus...@gmail.com
wrote:
On Tue, Jun 18, 2013 at 5:39 PM, Serge Hallyn
Hello Serge,
On Mon, Jun 17, 2013 at 4:43 PM, Serge Hallyn serge.hal...@ubuntu.com wrote:
Haven't tested, but the following should fix it:
Unfortunately, your patch didn't fix it. I put a fprintf in lxcapi_destroy:
if (r) {
fprintf(stderr,!!! removing %s for %s
Quoting zoolook (nbensa+lxcus...@gmail.com):
Hello Serge,
On Mon, Jun 17, 2013 at 4:43 PM, Serge Hallyn serge.hal...@ubuntu.com wrote:
Haven't tested, but the following should fix it:
Unfortunately, your patch didn't fix it. I put a fprintf in lxcapi_destroy:
if (r) {
On Tue, Jun 18, 2013 at 1:09 PM, Serge Hallyn serge.hal...@ubuntu.com wrote:
Though, I'm currently trying to reproduce with the lxc in ubuntu-lxc
saucy ppa, and failing. It's not deleting the original lv for me. I
just see:
Maybe the fact that I don't use the default lxc vg name? :-)
I can
Quoting zoolook (nbensa+lxcus...@gmail.com):
On Tue, Jun 18, 2013 at 1:09 PM, Serge Hallyn serge.hal...@ubuntu.com wrote:
Though, I'm currently trying to reproduce with the lxc in ubuntu-lxc
saucy ppa, and failing. It's not deleting the original lv for me. I
just see:
Maybe the fact
On Tue, Jun 18, 2013 at 5:39 PM, Serge Hallyn serge.hal...@ubuntu.com wrote:
Quoting zoolook (nbensa+lxcus...@gmail.com):
On Tue, Jun 18, 2013 at 1:09 PM, Serge Hallyn serge.hal...@ubuntu.com
wrote:
Though, I'm currently trying to reproduce with the lxc in ubuntu-lxc
saucy ppa, and
Hi Serge,
On Tue, Jun 18, 2013 at 5:57 PM, zoolook nbensa+lxcus...@gmail.com wrote:
On Tue, Jun 18, 2013 at 5:39 PM, Serge Hallyn serge.hal...@ubuntu.com wrote:
Exactly what code (git commit id or distro+pkg) are you using?
Installed: 0.9.0.0~staging~20130612-1544-0ubuntu1~ppa1~raring1
on
Hello,
this is one is weird. lxc-clone removes the original volume if there's
no space to create a snapshot for the clone
ii lxc 0.9.0.0~staging~2013 amd64
Linux Containers userspace tools
sysadmin@lxc0:~$ sudo lxc-clone -s -B lvm -p /srv/lxc -P /srv/lxc -o
I have a service that is running inside container perfectly. I had deployed
it using node.js package manager (npm). Now I wanted to run the service on
the host itself instead of the container due to some disk space issues I am
running into.
Is there a way like lxc-clone that clones the container
On Mon, Jul 30, 2012 at 9:59 AM, calerius D'Souza caler...@gmail.com wrote:
I have a service that is running inside container perfectly. I had deployed
it using node.js package manager (npm). Now I wanted to run the service on
the host itself instead of the container due to some disk space
Quoting Ramez Hanna (rha...@informatiq.org):
Hi,
I have started using lxc to setup a pre-production system instead of KVM
at first glance clone seemd to me that it would copy everything to a new roots
but turns out that in case of LVM it will snapshot
AFAIK snapshots are meant more for
On Mon, Aug 29, 2011 at 4:19 PM, Serge Hallyn
serge.hal...@canonical.com wrote:
Quoting Ramez Hanna (rha...@informatiq.org):
Hi,
I have started using lxc to setup a pre-production system instead of KVM
at first glance clone seemd to me that it would copy everything to a new
roots
but turns
Hi,
I have started using lxc to setup a pre-production system instead of KVM
at first glance clone seemd to me that it would copy everything to a new roots
but turns out that in case of LVM it will snapshot
AFAIK snapshots are meant more for backup or testing some changes and
discarding them
Hi Daniel,
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
+echo Tweaking configuration
+cp $lxc_path/$lxc_orig/config $lxc_path/$lxc_new/config
+sed -i '/lxc.utsname/d' $lxc_path/$lxc_new/config
+echo lxc.utsname = $hostname $lxc_path/$lxc_new/config
We should not assume lxc.utsname is
On 04/06/2011 04:05 PM, Serge E. Hallyn wrote:
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
What do you think is the best way to do this? We could allow the user
to specify a 'firstboot' script, which gets copied into root directory
of the container. Maybe boot the container when it's
On 04/05/2011 02:52 PM, Serge Hallyn wrote:
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
I think more configuration tweaking will be needed but this patch
looks good for me.
I'm hoping to set up a machine on which to play with lxc on btrfs
snapshots sometime this week. (In the
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
What do you think is the best way to do this? We could allow the user
to specify a 'firstboot' script, which gets copied into root directory
of the container. Maybe boot the container when it's done, run
/firstboot.sh, and shut down. Or just
On 03/30/2011 06:29 PM, Serge E. Hallyn wrote:
I've replaced most of my previous use of kvm and cloud instances for bug
investigations with lxc instances. To emulate my older workflows, I've
created lxc-clone. My diff against the current natty lxc package is
attached. I've written up how I
I saw this on the blog. Very useful and time saver. Exactly what alot of
pople were looking for.
On Wed, Mar 30, 2011 at 7:29 PM, Serge E. Hallyn serge.hal...@ubuntu.comwrote:
I've replaced most of my previous use of kvm and cloud instances for bug
investigations with lxc instances. To
I've replaced most of my previous use of kvm and cloud instances for bug
investigations with lxc instances. To emulate my older workflows, I've
created lxc-clone. My diff against the current natty lxc package is
attached. I've written up how I use this at s3hh.wordpress.com. Briefly,
I have a
25 matches
Mail list logo
