So what happens with the container's when the Host OS gets an upgrade that
includes a new kernel? Are the containers stil
reachable, runable, etc? I guess what I'm asking is what happens?
Dear Brian,
a new kernel will be not become used until you boot the host. From that, after
an os
'uptime' seems to be the uptime of the host, not of the guest. Is
that intended?
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how
On 12-09-10 02:02 PM, Dan Kegel wrote:
'uptime' seems to be the uptime of the host, not of the guest. Is
that intended?
uptime reads /proc/uptime which is gets you the time since the kernel
was started.
There are a few ways of fixing that issue:
- Implement a new time namespace allowing us
This is probably just a bad dream that will end when I move to
running lxc inside vmware instead of virtualbox.
I'm running Ubuntu 12.04.1 in Virtualbox, and inside that, Ubuntu 10.04 via
lxc-start-ephemeral, and inside that, a buildbot slave. I'm slowly working my
way through various issues
On 12-09-10 07:31 PM, Dan Kegel wrote:
This is probably just a bad dream that will end when I move to
running lxc inside vmware instead of virtualbox.
I'm running Ubuntu 12.04.1 in Virtualbox, and inside that, Ubuntu 10.04 via
lxc-start-ephemeral, and inside that, a buildbot slave. I'm
On 12-09-07 04:47 PM, Stéphane Graber wrote:
Hello everyone,
As you probably noticed Serge and I have been trying to keep up with all
the changes going to the lxc-users and lxc-devel mailing lists with some
varying success.
For quite a while now Serge has been maintaining a separate git
