On 02/20/2013 12:06 AM, Papp Tamas wrote:
On 02/19/2013 11:53 PM, Serge Hallyn wrote:
At this point, there will be a /var/lib/lxc/ltest/config which will
list lxc.rootfs = /var/lib/lxc/ltest/rootfs. So these steps are not
quite what you want.
Perhaps you just want to
sudo lxc-create
Quoting Papp Tamas (tom...@martos.bme.hu):
On 02/20/2013 12:06 AM, Papp Tamas wrote:
On 02/19/2013 11:53 PM, Serge Hallyn wrote:
At this point, there will be a /var/lib/lxc/ltest/config which will
list lxc.rootfs = /var/lib/lxc/ltest/rootfs. So these steps are not
quite what you want.
On 02/22/2013 03:22 PM, Serge Hallyn wrote:
About what? What I described above should work.
Yes, that's correct.
It doesn't (at least for me) that's why it is a bug, I guess;)
Note also that the staging branch now supports '-P|--lxcpath' for all
commands, so you could simply
sudo
Quoting Papp Tamas (tom...@martos.bme.hu):
On 02/22/2013 03:22 PM, Serge Hallyn wrote:
About what? What I described above should work.
Yes, that's correct.
It doesn't (at least for me) that's why it is a bug, I guess;)
Note also that the staging branch now supports '-P|--lxcpath' for
Oh, my recipe wasn't quite right - when you
sudo sed -i 's@/var/lib/lxc@/data/lxc@' /var/lib/lxc/r2/config
that also changes the path to r2's fstab. So either you have to
tweak the sed command, or
sudo mv /var/lib/lxc/r2/fstab /data/lxc/r2/
With that, it works for me.
-serge
On 02/22/2013 09:57 AM, Papp Tamas wrote:
On 02/22/2013 03:54 PM, Serge Hallyn wrote:
Why not?
Why would I do that?
It would just make myself confused.
I don't see any reason to do that.
tamas
The biggest reason for the lxcpath feature is the introduction of user
namespaces.
Once
On 02/22/2013 04:04 PM, Stéphane Graber wrote:
Once every user will be able to just run lxc containers, you don't want
them to have to check what container names the others are using to avoid
clashing with them.
I see, you're absolutely right.
It'd have been confusing to restrict system
On 02/22/2013 04:04 PM, Serge Hallyn wrote:
Oh, my recipe wasn't quite right - when you
sudo sed -i 's@/var/lib/lxc@/data/lxc@' /var/lib/lxc/r2/config
that also changes the path to r2's fstab. So either you have to
tweak the sed command, or
sudo mv /var/lib/lxc/r2/fstab
On 02/22/2013 10:20 AM, Papp Tamas wrote:
On 02/22/2013 04:04 PM, Stéphane Graber wrote:
Once every user will be able to just run lxc containers, you don't want
them to have to check what container names the others are using to avoid
clashing with them.
I see, you're absolutely right.
On 02/22/2013 04:49 PM, Stéphane Graber wrote:
We're planning on setting up a default lxcpath for user run containers,
-P will just be used to override this.
Excellent.
Thanks,
tamas
--
Everyone hates slow
So the info from where the container runs is in the per-container config.
Csordás Csaba Ifj.
On Tue, Feb 19, 2013 at 11:53 PM, Serge Hallyn serge.hal...@ubuntu.com wrote:
Quoting Papp Tamas (tom...@martos.bme.hu):
On 02/11/2013 04:11 AM, Serge Hallyn wrote:
Agreed, please do get us
Quoting Papp Tamas (tom...@martos.bme.hu):
On 02/11/2013 04:11 AM, Serge Hallyn wrote:
Agreed, please do get us precise reproduction steps so we can look into
it and fix it.
I'm sorry about the delay.
I tested is again and I'm quite surprised, that you're right. If it's at the
On 02/19/2013 11:53 PM, Serge Hallyn wrote:
At this point, there will be a /var/lib/lxc/ltest/config which will
list lxc.rootfs = /var/lib/lxc/ltest/rootfs. So these steps are not
quite what you want.
Perhaps you just want to
sudo lxc-create -n ltest -t ubuntu
sudo mkdir -p
On 02/11/2013 04:11 AM, Serge Hallyn wrote:
Agreed, please do get us precise reproduction steps so we can look into
it and fix it.
I'm sorry about the delay.
I tested is again and I'm quite surprised, that you're right. If it's at the
originial location,
then it just works fine.
If you can
14 matches
Mail list logo
