Serge,
On Sun, 2012-10-21 at 22:21 -0400, Michael H. Warfield wrote:
> On Sun, 2012-10-21 at 14:49 -0500, Serge Hallyn wrote:
> > Quoting Michael H. Warfield (m...@wittsend.com):
> > > Serge,
> > >
>
> ...
>
> > > Short of building a custom systemd, I don't know how to fix that problem
> > > an
On Sun, 2012-10-21 at 14:49 -0500, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > Serge,
> >
...
> > Short of building a custom systemd, I don't know how to fix that problem
> > and I suspect this OP is going to run into this same thing (container
> > taking over host
On Mon, 2012-10-22 at 02:53 +0200, Kay Sievers wrote:
> On Sun, Oct 21, 2012 at 11:25 PM, Michael H. Warfield
> wrote:
> > This is being directed to the systemd-devel community but I'm cc'ing the
> > lxc-users community and the Fedora community on this for their input as
> > well. I know it's no
On Sun, 2012-10-21 at 14:49 -0500, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > Serge,
> >
> > I'm going to top post here simply because this is going to go off in a
> > different direction and bringing in an old thread but it is related...
> >
> > Back on February 1
Hello,
This is being directed to the systemd-devel community but I'm cc'ing the
lxc-users community and the Fedora community on this for their input as
well. I know it's not always good to cross post between multiple lists
but this is of interest to all three communities who may have valuable
inp
Quoting John (l...@jelmail.com):
> On 19/10/12 16:51, Serge Hallyn wrote:
> >
> > Add:
> >
> > lxc.network.type = empty
> >
> > If you don't have any lxc.network.type sections, then the container
> > shares network with the host, and so the container talks to the host's
> > systemd. (same with ups
Quoting Michael H. Warfield (m...@wittsend.com):
> Serge,
>
> I'm going to top post here simply because this is going to go off in a
> different direction and bringing in an old thread but it is related...
>
> Back on February 14 you responded to a message about Fedora 16 in a
> container, which
On 19/10/12 16:51, Serge Hallyn wrote:
>
> Add:
>
> lxc.network.type = empty
>
> If you don't have any lxc.network.type sections, then the container
> shares network with the host, and so the container talks to the host's
> systemd. (same with upstart)
>
>
Thanks for the reply, I will try that tom
Laptop (Linux 3.2.0-25-generic x86_64)
$ ls /proc/self/ns
ipc net uts
Desktop (Linux 3.5.0-17-generic x86_64)
$ ls /proc/self/ns
ipc net uts
Do you have links to the kernel sources + patches that I need in for
lxc-attach to work?
Also, where is the official lxc repo located? Github, so
On Sun, Oct 21, 2012 at 4:41 PM, C. L. Martinez wrote:
If you HAVE used the default config file created by the template, but
it still doesn't work, you should probably contact the template
creator directly (it's on top of the template file) and ask them how
to use the template.
On Sun, Oct 21, 2012 at 9:27 AM, Fajar A. Nugraha wrote:
> On Sun, Oct 21, 2012 at 4:23 PM, C. L. Martinez wrote:
>> On Sun, Oct 21, 2012 at 9:20 AM, Fajar A. Nugraha wrote:
> --
No, problem continues ... I have used this template to create my lxc
container:
>>>
>>> In that I
On Sun, Oct 21, 2012 at 4:23 PM, C. L. Martinez wrote:
> On Sun, Oct 21, 2012 at 9:20 AM, Fajar A. Nugraha wrote:
--
>>>
>>> No, problem continues ... I have used this template to create my lxc
>>> container:
>>
>> In that I says use the unmodified config file first. For example, it
>> says
On Sun, Oct 21, 2012 at 9:20 AM, Fajar A. Nugraha wrote:
>>> --
>>
>> No, problem continues ... I have used this template to create my lxc
>> container:
>
> In that I says use the unmodified config file first. For example, it
> says "lxc.devttydir = lxc" (which you commented out).
>
> If you HAVE
On Sun, Oct 21, 2012 at 4:14 PM, C. L. Martinez wrote:
> On Sun, Oct 21, 2012 at 8:51 AM, Fajar A. Nugraha wrote:
>> On Sun, Oct 21, 2012 at 3:46 PM, Fajar A. Nugraha wrote:
lxc-start 1350808610.466 WARN lxc_conf - rootfs specified
but no console found at '/usr/lib64/lxc/root
On Sun, Oct 21, 2012 at 8:51 AM, Fajar A. Nugraha wrote:
> On Sun, Oct 21, 2012 at 3:46 PM, Fajar A. Nugraha wrote:
>>> lxc-start 1350808610.466 WARN lxc_conf - rootfs specified
>>> but no console found at '/usr/lib64/lxc/rootfs/dev/console'
>>
>> Does /usr/lib64/lxc/rootfs/dev/console
On Sun, Oct 21, 2012 at 3:46 PM, Fajar A. Nugraha wrote:
>> lxc-start 1350808610.466 WARN lxc_conf - rootfs specified
>> but no console found at '/usr/lib64/lxc/rootfs/dev/console'
>
> Does /usr/lib64/lxc/rootfs/dev/console exists?
Sorry. It should be "does /dev/console exists under you
On Sun, Oct 21, 2012 at 3:42 PM, C. L. Martinez wrote:
> Hi all,
>
> I have setup my first OL6 container but it doesn't starts.
How?
> lxc-start 1350808610.466 WARN lxc_conf - rootfs specified
> but no console found at '/usr/lib64/lxc/rootfs/dev/console'
Does /usr/lib64/lxc/rootfs/de
Hi all,
I have setup my first OL6 container but it doesn't starts. When I
launch lxc-start command, nothing appears:
[root@ol6host templates]# lxc-start -n ol6vmserver -o /tmp/ol.log
--logpriority=DEBUG
My config is:
# Container configuration for Oracle Linux 6
lxc.arch = x86_64
lxc.utsname =
18 matches
Mail list logo
