Quoting Scott Moser (smo...@ubuntu.com):
> prior to my enabling of the clone hook, the setting of the hostname
> was being done by writing to /etc/hostname. Instead of relying on that
> we're now writing 'local-hostname' into the metadata for the instance.
>
> cloud-init then reads this and sets
prior to my enabling of the clone hook, the setting of the hostname
was being done by writing to /etc/hostname. Instead of relying on that
we're now writing 'local-hostname' into the metadata for the instance.
cloud-init then reads this and sets the hostname properly.
We are also writing /etc/ho
Hi everyone!
We [1] have been working on bringing lightweight virtualization to
Linux-based mobile devices like Android (or other Linux-based devices with
diverse I/O) and want to share our solution: device namespaces.
Imagine you could run several instances of your favorite mobile OS or other
di
Quoting Oren Laadan (or...@cellrox.com):
> Hi everyone!
>
> We [1] have been working on bringing lightweight virtualization to
> Linux-based mobile devices like Android (or other Linux-based devices with
> diverse I/O) and want to share our solution: device namespaces.
>
> Imagine you could run s
On Thu, 22 Aug 2013, Serge Hallyn wrote:
> Quoting Scott Moser (smo...@ubuntu.com):
> > prior to my enabling of the clone hook, the setting of the hostname
> > was being done by writing to /etc/hostname. Instead of relying on that
> > we're now writing 'local-hostname' into the metadata for the i
Normal lxc-start usage tends to be "lxc-start -n name [-P lxcpath]".
This causes $lxcpath/$name/config to be the configuration for the
container. However, lxc-start is more flexible than that. You can
specify a custom configuration file, in which case $lxcpath/$name/config
is not used. You can a
Quoting Christian Seiler (christ...@iwakd.de):
> Hi Serge,
>
> >Ok, how about we make the system-cgroup-dir configurable in
> >/etc/lxc/lxc.conf? So if you have
> >
> > lxc.system-cgroup-dir = /machine
> >
> >then root-created containers will end up in /machine (or, if you're
> >already neste
Quoting Scott Moser (smo...@ubuntu.com):
> prior to my enabling of the clone hook, the setting of the hostname
> was being done by writing to /etc/hostname. Instead of relying on that
> we're now writing 'local-hostname' into the metadata for the instance.
>
> cloud-init then reads this and sets
prior to my enabling of the clone hook, the setting of the hostname
was being done by writing to /etc/hostname. Instead of relying on that
we're now writing 'local-hostname' into the metadata for the instance.
cloud-init then reads this and sets the hostname properly.
The one caveat is that sett
Hi Serge,
> Ok, how about we make the system-cgroup-dir configurable in
> /etc/lxc/lxc.conf? So if you have
>
> lxc.system-cgroup-dir = /machine
>
> then root-created containers will end up in /machine (or, if you're
> already nested under /lxc/m1, then /lxc/m1/machine). If that is
> unset
On Wed, Aug 21, 2013 at 9:22 AM, Gao feng wrote:
> On 08/21/2013 03:06 PM, Eric W. Biederman wrote:
>> I suspect libvirt should simply not share /run or any other normally
>> writable directory with the host. Sharing /run /var/run or even /tmp
>> seems extremely dubious if you want some kind of
11 matches
Mail list logo
