Great!
I already had that done that way since a few days ago.
rpm -qa | grep lxc
lxc-1.0.3-1.fc20.x86_64
lxc-devel-1.0.3-1.fc20.x86_64
lxc-debuginfo-1.0.3-1.fc20.x86_64
lxc-libs-1.0.3-1.fc20.x86_64
libvirt-daemon-driver-lxc-1.1.3.5-1.fc20.x86_64
I did create the Fedora container without a glitch.
On Tue, 2014-05-13 at 20:45 -0400, CDR wrote:
> I copied your file, copy-paste, and the file ended in
> /usr/share/lxc/templates/lxc-fedora20
... NO!!!
> Then chmod +x
> then lxc-create -t fedora20 -n masterfe
> Am I wrong?
Unbelievable wrong. You should have never done that.
Whatever you've
I copied your file, copy-paste, and the file ended in
/usr/share/lxc/templates/lxc-fedora20
Then chmod +x
then lxc-create -t fedora20 -n masterfe
Am I wrong?
On Tue, May 13, 2014 at 8:39 PM, Michael H. Warfield wrote:
> On Tue, 2014-05-13 at 20:30 -0400, CDR wrote:
>> I am trying to create a n
On Tue, 2014-05-13 at 20:30 -0400, CDR wrote:
> I am trying to create a new container inside a Fedora 20 box, fully updated.
> It blows up immediately.
> I can give you access if you wish. Maybe we can make a better template.
> Note: I am root.
> uname -r
> 3.14.3-200.fc20.x86_64
>
>
> lxc-create
I am trying to create a new container inside a Fedora 20 box, fully updated.
It blows up immediately.
I can give you access if you wish. Maybe we can make a better template.
Note: I am root.
uname -r
3.14.3-200.fc20.x86_64
lxc-create -t fedora20 -n masterfe
Host CPE ID from /etc/os-release: cpe:/
On Tue, 2014-05-13 at 20:03 -0400, CDR wrote:
> I decided to generate a new container and reinstall all my apps.
> A lot of work, but you successfully demolished all my work so far, for
> which I am thankful.
Well, we don't mean to demolish others efforts but we have put a lot of
work into these
I decided to generate a new container and reinstall all my apps.
A lot of work, but you successfully demolished all my work so far, for
which I am thankful.
Philip
On Tue, May 13, 2014 at 7:57 PM, Michael H. Warfield wrote:
> On Tue, 2014-05-13 at 18:13 -0400, CDR wrote:
>> Dear Mike
>> You ar
On Tue, 2014-05-13 at 18:13 -0400, CDR wrote:
> Dear Mike
> You are right, I only see one line.
> ls rootfs/etc/systemd/system/getty.target.wants -l
> total 0
> lrwxrwxrwx 1 root root 38 Apr 30 11:16 getty@tty1.service ->
> /usr/lib/systemd/system/getty@.service
Ok...
> You wouldn't have the sc
On Wed, May 14, 2014 at 5:13 AM, CDR wrote:
> Dear Mike
> You are right, I only see one line.
>
> ls rootfs/etc/systemd/system/getty.target.wants -l
> total 0
> lrwxrwxrwx 1 root root 38 Apr 30 11:16 getty@tty1.service ->
> /usr/lib/systemd/system/getty@.service
>
> You wouldn't have the script to
Dear Mike
You are right, I only see one line.
ls rootfs/etc/systemd/system/getty.target.wants -l
total 0
lrwxrwxrwx 1 root root 38 Apr 30 11:16 getty@tty1.service ->
/usr/lib/systemd/system/getty@.service
You wouldn't have the script to fix this around?
I created my Fedora 20 containers from wit
Quoting Harald Dunkel (harald.dun...@aixigo.de):
> Hi folks,
>
> Using the HEAD of the stable-1.0 branch:
>
> Sometimes lxc-start gets stuck. I haven't found a reliable
> way to reproduce this (yet), but it seems to be related to
> starting and stopping a lot of almost identical LXCs in
> paralle
Let me digest all this.
You must be right, because Fedora 20 containers are the only ones that
use systemd, in my box
many thanks
Federico
On Tue, May 13, 2014 at 1:24 PM, Michael H. Warfield wrote:
> On Tue, 2014-05-13 at 13:00 -0400, CDR wrote:
>> I am forced to use libvirt-lxc only because n
On Tue, 2014-05-13 at 13:00 -0400, CDR wrote:
> I am forced to use libvirt-lxc only because nobody can help me solve
> this issue. If somebody can figure this out, then I will only use lXC.
> In a Fedora20 container, if I start it with the "-d" flag, then it
> never let's me enter the container via
I am forced to use libvirt-lxc only because nobody can help me solve
this issue. If somebody can figure this out, then I will only use lXC.
In a Fedora20 container, if I start it with the "-d" flag, then it
never let's me enter the container via the console, it times out on me
when I use
lxc-consol
On Tue, May 13, 2014 at 12:29:07PM -0400, Michael H. Warfield wrote:
> On Tue, 2014-05-13 at 12:09 -0400, CDR wrote:
> > Dear Friends
> > I have a Fedora 20 LXC (libirt) container in production and I cannot reboot
> > it.
> > So I used "virsh edit mycontainer" and added several
> >
> >
> >
On Tue, 2014-05-13 at 12:09 -0400, CDR wrote:
> Dear Friends
> I have a Fedora 20 LXC (libirt) container in production and I cannot reboot
> it.
> So I used "virsh edit mycontainer" and added several
>
>
>
>
>
Ok... But that's libvirt LXC, not LXC-Tools LXC.
> The problem i
Hi Stéphane,
sounds great! Testing...
Regards,
Flo
On Tue, May 13, 2014 at 11:52 AM, Stéphane Graber wrote:
> On Tue, May 13, 2014 at 09:40:47AM +0200, Flo wrote:
> > Hi,
> >
> > are there any plans to backport LXC 1.0.3 for Ubuntu 12.04? Maybe kernel
> > 3.13 is needed (linux-image-generic-lt
Dear Friends
I have a Fedora 20 LXC (libirt) container in production and I cannot reboot it.
So I used "virsh edit mycontainer" and added several
The problem is that after it gets saved, the new interfaces never show
up in ip link, and I have no idea how to make Fedora under L
On Tue, 2014-05-13 at 17:03 +0200, Harald Dunkel wrote:
> Hi folks,
> Using the HEAD of the stable-1.0 branch:
> Sometimes lxc-start gets stuck. I haven't found a reliable
> way to reproduce this (yet), but it seems to be related to
> starting and stopping a lot of almost identical LXCs in
> para
Hi folks,
Using the HEAD of the stable-1.0 branch:
Sometimes lxc-start gets stuck. I haven't found a reliable
way to reproduce this (yet), but it seems to be related to
starting and stopping a lot of almost identical LXCs in
parallel without sleep in between (e.g. 8 containers with
Centos 6.x).
On Tue, May 13, 2014 at 09:40:47AM +0200, Flo wrote:
> Hi,
>
> are there any plans to backport LXC 1.0.3 for Ubuntu 12.04? Maybe kernel
> 3.13 is needed (linux-image-generic-lts-trusty)?
>
> Regards,
> Flo
It's planned though I haven't yet got around to it.
In the mean time, you may use ppa:ubu
Hi,
are there any plans to backport LXC 1.0.3 for Ubuntu 12.04? Maybe kernel
3.13 is needed (linux-image-generic-lts-trusty)?
Regards,
Flo
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
22 matches
Mail list logo
