On Tue, Sep 1, 2015 at 12:35 PM, Peter Steele wrote:
>
> Is there a recommended prefix for the auto-generated lxc mac addresses?
>
>
These links should be relevant:
http://wiki.xenproject.org/wiki/Xen_Networking#MAC_addresses
http://askubuntu.com/questions/139069/why-does-virt-install-man-page-re
On 08/31/2015 10:03 PM, Serge Hallyn wrote:
Right - if you use lxc-create to create the config file, and your
initial lxc.conf (i.e. /etc/lxc/default.conf or whatever you pass
as CONF to lxc-create -f CONF) contains something like
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
then your container confi
On 08/31/2015 08:41 PM, Fajar A. Nugraha wrote:
Nope. lxc.cgroup allows you to create and access the block device, but
you still need to create the device node yourself.
Fair enough. Then I guess I'll use mknod...
___
lxc-users mailing list
lxc-users@
Quoting Benoit GEORGELIN - Association Web4all (benoit.george...@web4all.fr):
> I do start them as non-root user because I tough I was the only way to start
> an unprivileged container on the system.
Ok, that's what I was wondering. In order to start such containers
as root, you only need to ma
Quoting Fajar A. Nugraha (l...@fajar.net):
> On Tue, Sep 1, 2015 at 3:23 AM, Peter Steele wrote:
>
> > On 08/31/2015 06:32 AM, Serge Hallyn wrote:
> >
> >>
> >> Should show up in a line like
> >>
> >> lxc.network.hwaddr = 00:16:3e:83:d1:8f
> >>
> >> in the created container config.
> >> _
On Tue, Sep 1, 2015 at 9:19 AM, Federico Alves wrote:
> I did a live-upgrade from FC20 to 21 and the issue faded away.
> Thanks for the comments.
>
>
Glad to hear that.
Be aware though that F21 will reach end of life around december this year.
--
Fajar
> On Mon, Aug 31, 2015 at 9:50 PM, Faj
On Tue, Sep 1, 2015 at 4:13 AM, Peter Steele wrote:
> lxc.cgroup.devices.allow = b 8:3 rwm
>
> and restarted my container. This didn't seem to do the trick through.
> Running this command on the host however did do the trick:
>
> # mknod -m 777 /var/lib/lxc/test/rootfs.dev/sda3 b 8 3
>
> I assume
On Tue, Sep 1, 2015 at 3:23 AM, Peter Steele wrote:
> On 08/31/2015 06:32 AM, Serge Hallyn wrote:
>
>>
>> Should show up in a line like
>>
>> lxc.network.hwaddr = 00:16:3e:83:d1:8f
>>
>> in the created container config.
>> ___
>> lxc-users mailing list
I did a live-upgrade from FC20 to 21 and the issue faded away.
Thanks for the comments.
On Mon, Aug 31, 2015 at 9:50 PM, Fajar A. Nugraha wrote:
> On Tue, Sep 1, 2015 at 6:01 AM, Federico Alves wrote:
>
>> The issue is that Asterisk. my app does not compile in FC 22.
>> I am researching to how
On Tue, Sep 1, 2015 at 6:01 AM, Federico Alves wrote:
> The issue is that Asterisk. my app does not compile in FC 22.
> I am researching to how proceed
>
>
A quick search found this ubuntu ppa, so if you switch to ubuntu trusty you
might not need to compile anything at all:
https://launchpad.net/
I do start them as non-root user because I tough I was the only way to start an
unprivileged container on the system.
benoit@lxd-virt-01a:~$ lxc-ls -f
NAME STATE IPV4 IPV6 GROUPS AUTOSTART
--
benoit RUNNING IP_ADDRESS - - NO
jordan STOPPED
The issue is that Asterisk. my app does not compile in FC 22.
I am researching to how proceed
On Mon, Aug 31, 2015 at 4:21 PM, Fajar A. Nugraha wrote:
> On Tue, Sep 1, 2015 at 1:29 AM, Federico Alves wrote:
>
>> I get this crash every few minutes
>> [619187.189766] systemd-coredump[1309752]: Fa
can any one know a solution for this ?
I am trying to run docker with lxc driver and ended up in weird problem.
lxc-start: conf.c: mount_entry: 2049 No such file or directory - failed to
mount 'tmpfs' on '/usr/lib64/lxc/rootfs///run'
lxc-start: conf.c: lxc_setup: 4163 failed to setup the mount
This is likely a newbie question but here goes...
I have some privileged containers that need access to certain block
devices available on their host. For example, I'd like /dev/sda3 to be
accessible from my container test. The major/minor values for this
device is:
# ll /dev/sda3
brw-rw
On 08/31/2015 06:32 AM, Serge Hallyn wrote:
Should show up in a line like
lxc.network.hwaddr = 00:16:3e:83:d1:8f
in the created container config.
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo
On Tue, Sep 1, 2015 at 1:29 AM, Federico Alves wrote:
> I get this crash every few minutes
> [619187.189766] systemd-coredump[1309752]: Failed to get COMM, falling
> back to the command line.
> [619187.189787] systemd-coredump[1309752]: Failed to get EXE.
>
> The host is FC 22 and the LXC-Contain
Quoting Benoit GEORGELIN - Association Web4all (benoit.george...@web4all.fr):
> unfortunately, it's the only way to allow custom network configuration from
> an unprivileged exactly how lxc add the network interface into the Ovs switch
> .
>
> My design is this one , I use openvswitch for the n
I get this crash every few minutes
[619187.189766] systemd-coredump[1309752]: Failed to get COMM, falling back
to the command line.
[619187.189787] systemd-coredump[1309752]: Failed to get EXE.
The host is FC 22 and the LXC-Container is FC 20
At the container I have
rpm -qa | grep systemd
systemd
On Tue, Sep 01, 2015 at 03:01:07AM +1000, overlay fs wrote:
> The bug,
>
> 'Failed to whiteout' error in Trusty with 3.19 kernel
> https://lists.linuxcontainers.org/pipermail/lxc-users/2015-August/009854.html
> https://bugs.launchpad.net/lxc/+bug/1486073
> https://bugs.launchpad.net/ubuntu/+source
unfortunately, it's the only way to allow custom network configuration from an
unprivileged exactly how lxc add the network interface into the Ovs switch .
My design is this one , I use openvswitch for the newtorking
log on the system as user : non-root
start your container: lxc-start -n unpr
The bug,
'Failed to whiteout' error in Trusty with 3.19 kernel
https://lists.linuxcontainers.org/pipermail/lxc-users/2015-August/009854.html
https://bugs.launchpad.net/lxc/+bug/1486073
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490267
is present in lxc versions 1.0.7 and 1.0.8, but see
hello
I have a problem after updating "apt-get upgrade" on ubuntu vivid
invoke-rc.d: initscript lxc-net, action "start" failed.
dpkg: error processing package lxc (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
lxc
Greetings, Peter Steele!
> On 08/30/2015 04:37 PM, Andrey Repin wrote:
>> Please start from the beginning.
>> What network topology you want for your containers, and what specific
>> features
>> you need from VETH interface, that other networking modes do not offer?
> I'm using host bridging wit
On Mon, Aug 31, 2015 at 11:02:21AM -0500, Luis M. Ibarra wrote:
> Have you checked juju? I don't think there's a driver for LXD only LXC but
> they have plans to add it.
Yep, I've done the initial implementation here,
https://github.com/juju/juju/pull/2913
> It's web based, but it can scale up.
Have you checked juju? I don't think there's a driver for LXD only LXC but
they have plans to add it.
It's web based, but it can scale up.
2015-08-31 10:50 GMT-05:00 Stéphane Graber :
> On Mon, Aug 31, 2015 at 11:39:42AM -0400, Federico Alves wrote:
> > Is there GUI for LXD that can give you a s
On Mon, Aug 31, 2015 at 11:39:42AM -0400, Federico Alves wrote:
> Is there GUI for LXD that can give you a single pane of glass with all your
> datacenter, considering you may have hundreds of servers and thousands of
> containers?
> Sort of Vmware Vcenter app, not web interface,but a real windows
Is there GUI for LXD that can give you a single pane of glass with all your
datacenter, considering you may have hundreds of servers and thousands of
containers?
Sort of Vmware Vcenter app, not web interface,but a real windows app?
I would pay any money for that.
___
On Mon, Aug 31, 2015 at 02:57:15PM +0100, Thouraya TH wrote:
> Hello all :)
>
> Here is my script: i try to do the dumping process in parallel with its
> running
>
> #!/bin/bash
> if [ $# -ne 1 ]
> then
> echo "USE: ./Dumping.sh worker-name"
> else
>
> lxc-start -n $1 *& my_pid=$!*
> sleep 10
Quoting Tamas Papp (tom...@martos.bme.hu):
>
>
> On 08/28/2015 03:48 PM, Serge Hallyn wrote:
> >Quoting Tamas Papp (tom...@martos.bme.hu):
> >>hi,
> >>
> >>I would like to achieve, what is in subject.
> >>
> >>
> >>However, I cannot get over on this apparmor issue:
> >>
> >>[7690496.246952] type=
the cgroup info is contained in the container configuration file. So make
sure to copy that and not just the container rootfs.
-serge
Quoting Pablo Silva (psil...@gmail.com):
> Thanks Serge! for your response..
>
> We want to move a stop container from hosta to host b, my big question is,
> sim
Thanks Serge! for your response..
We want to move a stop container from hosta to host b, my big question is,
simply make a copy rsync or I should also copy the cgroups information to
the host b?
-Pablo
On Mon, Aug 31, 2015 at 10:47 AM, Serge Hallyn
wrote:
> Quoting Pablo Silva (psil...@gmail.c
Quoting Pablo Silva (psil...@gmail.com):
> Dear colleagues:
>
> I need to know how to move a container that is on host1 host2 towards.
>
> I can use lxc-clone or just rsync is from host1 to host2 ?, what
> happens to the information generated in / cgrups?
Wait, do you want to copy a ru
Quoting Benoit GEORGELIN - Association Web4all (benoit.george...@web4all.fr):
> Hi,
>
> I would like to know if there is an alternative option of
> lxc.network.script.up with an unprivileged containter.
No. You'll need to start the container as root to do that - else you're
allowing an unpriv
Quoting Peter Steele (pwste...@gmail.com):
> On 08/30/2015 11:10 AM, Peter Steele wrote:
> >Clearly there is user error here on my part and I am not correctly
> >specifying how to configure LXC containers to use host bridging
> >under CentOS. I'll have to do some more digging.
> >
>
> I figured it
Quoting Peter Steele (pwste...@gmail.com):
> Is there a way to determine the auto-generated MAC address that
> lxc-create assigns to a container, apart from starting it and
> inspecting the live container?
Should show up in a line like
lxc.network.hwaddr = 00:16:3e:83:d1:8f
in the created contai
On 08/28/2015 03:48 PM, Serge Hallyn wrote:
Quoting Tamas Papp (tom...@martos.bme.hu):
hi,
I would like to achieve, what is in subject.
However, I cannot get over on this apparmor issue:
[7690496.246952] type=1400 audit(1440757904.938:1130):
apparmor="DENIED" operation="mount" info="failed
On Sat, Aug 29, 2015 at 12:31 AM, Serge Hallyn wrote:
> Can you tell me where you got the kernel? I haven't yet reproduced.
Upstream Kernel source is here:
https://git.kernel.org/cgit/linux/kernel/git/rt/linux-stable-rt.git/
We are using the code from tag: v3.12.33-rt47
The config we are using
37 matches
Mail list logo
