Greetings, first post to the list.
I’ve been doing some initial research, started with docker and also LXC by way
of Proxmox (which I use for virtualization).
Basically, I’m looking at rolling out Freeswitch for a whole bunch of my
customers in an automated fashion, and using containers, whet
If you have a Canonical support contract you should probably go through its
regular support channel, instead of this mailinglist or github.
Op 8 nov. 2016 06:03 schreef "Saint Michael" :
> Stephane Grabber closed my report without investigating the evidence. He
> says it is a firewall or a Kernel
On Tue, Nov 08, 2016 at 03:00:48AM +, Christian Tardif wrote:
> Hi,
>
> I just faced a strange issue with LXD containers. I'm using them quite
> extensively, but never faced that before. Normally, the userID that are
> presented to the container (they're coming from SSSD with ActiveDirectory
>
Stephane Grabber closed my report without investigating the evidence. He
says it is a firewall or a Kernel bug. If this a Kernel bug, he needs to
act, because I don't upgrade the Kernels, Ubuntu does it. And there is no
firewall in my LXC host.
I am complaining tomorrow to Canonical.
On Mon, Nov 7
I am not complaining about the master host, I cannot contact the containers
from the same network. That is the issue. The host is irrelevant. This
issue cannot be. It voids the whole technology.
On Mon, Nov 7, 2016 at 10:11 PM, Christian Tardif <
christian.tar...@servinfo.ca> wrote:
> Just want t
Just want to point out that the restriction only occurs between the host
and its containers. Outside of it, it can talk without problems.
Christian Tardif
-- Message d'origine --
De: "Christian Tardif"
À
This is normal behavior with both macvlan's and ipvlan's
Even if I have seen it working a few times, I can't explain the exact
details. But normally, MACVLAN and IPVLAN do not support communications
from and to the master host:
https://people.netfilter.org/pablo/netdev0.1/papers/IPVLAN-The-be
Hi,
I just faced a strange issue with LXD containers. I'm using them quite
extensively, but never faced that before. Normally, the userID that are
presented to the container (they're coming from SSSD with
ActiveDirectory backend) are relatively low... 2000, 3000, that kind
of ID's
Last fr
I already open a ticket
https://github.com/lxc/lxc/issues/1284
On Mon, Nov 7, 2016 at 1:43 PM, Saint Michael wrote:
> The issue is very simple, and it started a few days ago, after an update.
> You cannot communicate from the same network to a container, but from the
> container you can initiate
The issue is very simple, and it started a few days ago, after an update.
You cannot communicate from the same network to a container, but from the
container you can initiate any connection just fine.
Also from outside my network I can ssh into a container and ping. From the
same network I cannot e
LXC: https://github.com/lxc/lxc/issues/new
LXD: https://github.com/lxc/lxd/issues/new
(Be sure to know which project your issue applies to before opening an issue.)
Sean
On Mon, Nov 7, 2016 at 1:10 PM, Saint Michael wrote:
> Does anybody know how to open a bug with LXC?
> I cannot figure it ou
Greetings, Saint Michael!
> Does anybody know how to open a bug with LXC?
> I cannot figure it out. Ubuntu does point me to another site, but I cannot
> see how to open a new ticket.
LXC has a repo on GitHub. If you have GH account, you can file tickets.
--
With best regards,
Andrey Repin
M
On Mon, Nov 7, 2016 at 12:10 PM, Saint Michael wrote:
>
> Does anybody know how to open a bug with LXC?
> I cannot figure it out. Ubuntu does point me to another site, but I cannot
> see how to open a new ticket.
>
>
>
> ___
> lxc-users mailing list
> l
Does anybody know how to open a bug with LXC?
I cannot figure it out. Ubuntu does point me to another site, but I cannot
see how to open a new ticket.
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinf
Hi again,
problem solved thanks to a message on this thread :)
I simply added
lxc.network.link = eth0
Going to test for real then.
Regards
Le 07/11/2016 à 15:32, Vince a écrit :
> Hi all,
>
> Just discovered lxd yesterday, trying it out with great expectations !
>
> When I launch a container,
It is absolutely normal. The host is accessible as usual.
ip link
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth3: mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:5
Hi,
I use ubuntu 16.04. I'd look at net dev naming convention and your static
configurations
for instance:
ip link:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s25: mtu 1500 qdisc pfifo_fast
st
Since the last update to Ubuntu, now I cannot ping or ssh into any
container, from the same network. It seems the packets go to the router,
for I can ping and communicate to the containers from outside my network.
This problem did not happen until a few days ago.
My networking at the container l
Hi there,
I'have been attempting to use lxd on centos 7.2.1511 (kernel
3.10.0-327.36.2). I builded lxd successfully from source after
installation of lxc and lxc-devel distro pkgs (which are lxc 1.x
releases)...
Every aspects of lxd works except launching containters. I don't need to
enforc
Hi all,
Just discovered lxd yesterday, trying it out with great expectations !
When I launch a container, I get the message that it has no network
attached:
The container you are starting doesn’t have any network attached to it.
To create a new network, use: lxc network create
To attach a ne
20 matches
Mail list logo
