tart: failed to drop capabilities
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'test_1'
I not yet sure why this is happening. Do you know what might be causing
wrote:
> On 07/17/2013 10:01 PM, Jay Taylor wrote:
> > Hi,
> >
> > I'm not sure what I am doing wrong here.
> >
> > This is a EC2 VM with /var/lib/lxc linking to a mounted BTRFS volume.
> >
> > OS: Ubuntu 12.04 LTS
> > LXC Version: 0.9.0
> >
Yes, the actual name was "admin". Yikes. Is there a list of "don't do's"
anywhere?
On Wed, Jul 17, 2013 at 2:31 PM, Serge Hallyn wrote:
> Quoting Jay Taylor (j...@jaytaylor.com):
> > lxc.cap.drop = sys_module
> > lxc.cap.drop = mac_test_1
>
Out of curiosity, did you see it in the past before you you updated from
the PPA today?
On Wed, Jul 31, 2013 at 4:16 AM, Tamas Papp wrote:
> hi All,
>
> I've seen a couple of times in the past like this:
>
> # lxc-ls --fancy --stopped --fancy-format name,state
> NAME STATE
> ---
Greetings,
I am hitting a problem with LXC were it's assigned the same IP address to
different containers:
sendhub_important_v7_10010 RUNNING 10.0.3.141 - NO
sendhub_important_v7_10017 RUNNING 10.0.3.141 - NO
sendhub_important_v7_10023 RUNNING 10.0.3.141 - NO
sendhub_impor
Also, now when I try to clone "sendhub" to a new container, it doesn't even
get an IP address..
sendhub_important_v7_10300 RUNNING - - NO
On Fri, Aug 9, 2013 at 7:08 AM, Jay Taylor wrote:
> Greetings,
>
> I am hitting a problem with LXC were it's
produced across multiple hosts).
On Fri, Aug 9, 2013 at 8:02 AM, Serge Hallyn wrote:
> Quoting Jay Taylor (j...@jaytaylor.com):
> > Greetings,
> >
> > I am hitting a problem with LXC were it's assigned the same IP address to
> > different containers:
>
> How ar
at 8:52 AM, Jay Taylor wrote:
> Hi Serge,
>
> That's the thing..the containers all have unique addresses. They're being
> created by `lxc-clone -B btrfs -s -o base_container -n
>
> Now...every container I try to create or stop/start doesn't receive any IP
> a
ore?
On Fri, Aug 9, 2013 at 8:57 AM, Jay Taylor wrote:
> Also, here is one of the container configs:
>
> lxc.mount = /var/lib/lxc/sendhub_web_v7_10146/fstab
> lxc.tty = 4
> lxc.pts = 1024
> lxc.devttydir = lxc
> lxc.arch = x86_64
> lxc.logfile = /var/log/l
My reply is inline below.
On Fri, Aug 9, 2013 at 12:10 PM, Serge Hallyn wrote:
> Quoting Jay Taylor (j...@jaytaylor.com):
> > lxc.network.hwaddr = 00:16:3e:07:7b:8f
>
> Can you show the result of 'grep lxc.network.hwaddr /var/lib/lxc/*/config'?
>
ub
After further investigation yesterday, I am not convinced it is an
IP-address issue. The affected host machines are unable to start any
existing or newly created containers. The incident that triggered the
issue was cloning 1 container into 10 new ones, and then launching them all
simultaneously.
The systems all use btrfs volumes.
On Aug 10, 2013, at 3:59 PM, zoolook wrote:
> On Sat, Aug 10, 2013 at 7:40 PM, Jay Taylor wrote:
>> Are there any known concurrency issues with LXC which would
>> explain why executing a lot of clone/start LXC commands at the same time
>>
Thanks, will do this morning.
On Aug 12, 2013, at 6:10 AM, Serge Hallyn wrote:
> Quoting Jay Taylor (j...@jaytaylor.com):
>> After further investigation yesterday, I am not convinced it is an
>> IP-address issue. The affected host machines are unable to start any
>> exis
allyn wrote:
> Quoting Jay Taylor (j...@jaytaylor.com):
> > After further investigation yesterday, I am not convinced it is an
> > IP-address issue. The affected host machines are unable to start any
> > existing or newly created containers. The incident that triggered t
RUNNING - - NO
x9 RUNNING - - NO
On Wed, Aug 14, 2013 at 10:12 AM, Serge Hallyn wrote:
> Quoting Serge Hallyn (serge.hal...@ubuntu.com):
> > Quoting Jay Taylor (j...@jaytaylor.com):
> > > After further investigation yesterday, I am not conv
:22 PM, Jay Taylor wrote:
> Hi Serge,
>
> I added zfs support to the application and systems creating/hosting the
> containers, and I have subsequently been unable to reproduce any issues.
>
> As far as trying to reproduce it with btrfs, I've had some success.
>
>
My reply is inline below.
On Wed, Aug 14, 2013 at 1:30 PM, Serge Hallyn wrote:
> Quoting Jay Taylor (j...@jaytaylor.com):
> > Hi Serge,
> >
> > I added zfs support to the application and systems creating/hosting the
> > containers, and I have subsequently been una
Serge,
As requested, I've filed the issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214085
Best,
Jay
On Fri, Aug 16, 2013 at 9:08 AM, Serge Hallyn wrote:
> Quoting Jay Taylor (j...@jaytaylor.com):
> > I tried doing that, but it didn't work.
> >
> >
ding up to 5 retries,
it consistently eventually completely successfully.
Thanks for your advice!
Best,
Jay
On Tue, Aug 27, 2013 at 6:06 AM, Serge Hallyn wrote:
> Quoting Jay Taylor (j...@jaytaylor.com):
> > Greetings LXC folks,
> >
> > With LXC and ZFS on AWS, aft
Hi Srini,
Learning the iptables rules can be tricky at first, especially when you're
new to LXC. I highly recommend finding a way to automate the process.
Here is a real-world example of how iptables can be setup on a
per-container basis in LXC:
https://github.com/Sendhub/shipbuilder/blob/m
20 matches
Mail list logo
