Also, submitted a new issue: https://github.com/lxc/lxcfs/issues/217
On 27 September 2017 at 02:24, Stéphane Graber wrote:
> Hi,
>
> This sounds like a lxcfs issue.
>
> Can you file a bug at https://github.com/lxc/lxcfs or find one which
> matches your symptoms.
>
> We'll want at least:
>
> - /
Here I attach the 2 files with the output of those commands: one.txt is
right after I copied several gigabytes of files to that container (using
samba), two.txt is after I removed it.
It looks like the most relevant number that is changed is `total_cache`
On 27 September 2017 at 02:24, Stéphane G
Things look fine. I'm not sure why the kernel would still be looking at
eth0 when you specifically told it to setup the tunnel on eth1...
I wonder if adding a static route for the multicast address to go to
eth1 would fix that somehow.
On Tue, Sep 26, 2017 at 12:48:01PM -0400, Ron Kelley wrote:
Looks like I mistakenly said unicast. In fact, we are using multicast group IP
(239.0.0.1) to setup our VXLAN interfaces (please see below). Also, in the
example below, 10.250.1.21 is bound the eth0 (our management interface) and
172.18.22.21 is bound to eth1 (VXLAN interface). We have 8 serv
Hi,
Ok, so you're doing your own VXLAN youtside of LXD and then connecting
containers directly to it.
The kernel error is very odd for unicast vxlan... there's really no
reason for it to ever use the other interface...
So I'm assuming the 10.250.1.21 IP is on eth0 and 172.18.22.21 on eth1
(or th
Thanks Stephane.
Here is a “lxc network list” on the hosts:
rkelley@LXD-QA-Server-04:~$ lxc network list
++--+-+-+-+
| NAME | TYPE | MANAGED | DESCRIPTION | USED BY |
++--+-+-+-+
| eth0 | physical | NO
Hi,
This sounds like a lxcfs issue.
Can you file a bug at https://github.com/lxc/lxcfs or find one which
matches your symptoms.
We'll want at least:
- /proc/meminfo from the container
- /sys/fs/cgroup/memory/lxc/CONTAINER/memory.usage_in_bytes from the host
- /sys/fs/cgroup/memory/lxc/CONTAI
On Fri, Sep 22, 2017 at 02:29:15PM +, Laurent Ducos wrote:
> Hello
> After xenial ubuntu upgrade lxd switch to 2.18
> i reboot and no ip for lxdbr0 and no ip for container
> It set manualy ip for lxdbr0 "sudo ip addr add dev lxdbr0 10.215.181.1/24"
> and launch a container but always no ip
On Sat, Sep 23, 2017 at 01:04:41PM +1000, Michael Honeyman wrote:
> Hi lxc-users,
>
> I'm hoping someone wise can help me with some ideas how to solve this
> problem.
>
> I've been having fun trying to get Steam in Big Picture Mode working inside
> a LXD privileged container. The host is Ubuntu 1
On Sun, Sep 24, 2017 at 03:27:27PM -0400, Ron Kelley wrote:
> Greetings all,
>
> Trying to isolate a condition whereby a container providing firewall services
> seems to stop processing traffic for a short time. We keep getting the below
> information in /var/log/syslog of the server running th
When using LXD, there's no need to update any config, you only need to
restart the container so that LXD can re-generate the configuration for you.
(Unfortunately the LXC library can't know about this, so the warning
message may look a bit confusing)
On Mon, Sep 25, 2017 at 10:13:29PM -0400, Sain
Can you post the full "dnsmasq --version" output?
There was at least one issue when dnsmasq was complaining about some
wrong library version which was causing errors. I fixed that one and
updated the Ubuntu package, but that update also changes the code to
just ignore version parsing errors in gen
Hi Simos,
Thx for your answer. in fact, on friday lot's of people has issues with the
lxd update. I assume it's been fixed and patch because I have no issue
today.
I'll try to rebuild my cluster now
Thx a lot, and hope to see you soon, sad to not see you at UbuCon. Maybe
next year :)
Cheers,
Wi
13 matches
Mail list logo
