Re: [lxc-users] How to open a ticket with LXC

[Janjaap Bos]

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 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, 2016 at 1:49 PM, Saint Michael  wrote:
>
>> 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 any connection just fine.
>>> Also from outside my network I can ssh into a container and ping. From
>>> the same network I cannot even ping a container.
>>>
>>>
>>>
>>> On Mon, Nov 7, 2016 at 1:29 PM, Judd Meinders <
>>> judd.meind...@rockwellcollins.com> wrote:
>>>
 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
 > lxc-users@lists.linuxcontainers.org
 > http://lists.linuxcontainers.org/listinfo/lxc-users

 https://github.com/lxc/lxc/issues

 If you can, include steps to reproduce the issue, software versions,
 configs, workarounds, etc.  A well formed and organized issue will get
 more attention.

 --
 Judd Meinders
 ___
 lxc-users mailing list
 lxc-users@lists.linuxcontainers.org
 http://lists.linuxcontainers.org/listinfo/lxc-users
>>>
>>>
>>>
>>
>
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Wierd issue with high userID's

[Stéphane Graber]

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
> backend) are relatively low...   2000, 3000, that kind of ID's
> 
> Last friday, at the office, I built two containers (Ubuntu 16.04, CentOS
> 7.1) with the same kind of configuration regarding authentication; SSSD. And
> I notice that I wasn't able to log in via SSH. But one of my colleague was
> able to. We re-checke the config, just to make sure (but at the same time,
> it was impossible for this config to fail, as it is presented to the servers
> via Puppet. So the same config, and on the same OS level as other installs
> (we have numerous Ubuntu 16.04 with the same config, but the first one on
> LXD containers).
> 
> We were trying to find out what piece was missing when we discover that this
> is not just the logging that fails, but everything related to these high
> UserID's. They are coming from a calculation based on Windows SID's for the
> user, which gives a huge range of userID's, from a few thousands to tens, if
> not hundreds thousands.   So with my user, I can't set a permission with it,
> and I can't login.In fact, I don't exist with this user other than using
> "getent passwd", or "id".
> 
> What can be the cause? Something to do with namespaces, maybe?  cgroups?
> 
> We'ew in the dark. And until we can solve this, LXD containers aren't that
> helpful to us, unfortunately.
> 
> Christian Tardif

Hey there,

By default LXD uses a range of 65536 uid and gid as the user namespace
map for the containers.

This means that only uid 0 through 65536 exist in your container,
anything outside of that will be treated as invalid by the kernel.


sssd and similar authentication mechanisms will typically use uids/gids
above that POSIX range and so require you to grow the default map size
in /etc/subuid and /etc/subgid.


On the systems I use with sssd I typically just bump the allocation for
lxd and root in /etc/subuid and /etc/subgid from 65536 to 100 which
takes care of that problem.


-- 
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com


signature.asc
Description: PGP signature
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] How to open a ticket with LXC

[Saint Michael]

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, 2016 at 1:49 PM, Saint Michael  wrote:

> 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 any connection just fine.
>> Also from outside my network I can ssh into a container and ping. From
>> the same network I cannot even ping a container.
>>
>>
>>
>> On Mon, Nov 7, 2016 at 1:29 PM, Judd Meinders <
>> judd.meind...@rockwellcollins.com> wrote:
>>
>>> 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
>>> > lxc-users@lists.linuxcontainers.org
>>> > http://lists.linuxcontainers.org/listinfo/lxc-users
>>>
>>> https://github.com/lxc/lxc/issues
>>>
>>> If you can, include steps to reproduce the issue, software versions,
>>> configs, workarounds, etc.  A well formed and organized issue will get
>>> more attention.
>>>
>>> --
>>> Judd Meinders
>>> ___
>>> lxc-users mailing list
>>> lxc-users@lists.linuxcontainers.org
>>> http://lists.linuxcontainers.org/listinfo/lxc-users
>>
>>
>>
>
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Something catastrophic just happened to LXC networking

[Saint Michael]

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 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" 
> À: "LXC users mailing-list" 
> Envoyé : 2016-11-07 22:09:40
> Objet : Re: [lxc-users] Something catastrophic just happened to LXC
> networking
>
> 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-beginning.pdf
>
> --
>
> *Christian Tardif*
>
>
>
> -- Message d'origine --
> De: "Saint Michael" 
> À: "LXC users mailing-list" 
> Envoyé : 2016-11-07 10:57:43
> Objet : [lxc-users] Something catastrophic just happened to LXC networking
>
> ​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 level is:
>
> lxc.network.type=macvlan
> lxc.network.macvlan.mode=bridge
> lxc.network.link=eth0
> lxc.network.name = eth1
> lxc.network.flags=up
> lxc.network.hwaddr = mac.add.re.ss
> lxc.network.ipv4 = 0.0.0.0/24
>
> ​on the host, the interface eth0 is also used by the host, but I tried
> with another interface which is UP but it has no IP, and it still does not
> allow me to reach my containers, in fact taking my business down since I
> execute a lot of stuff remotely.
> Any idea?
>
> ​
>
>
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Something catastrophic just happened to LXC networking

[Christian Tardif]

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" 
À: "LXC users mailing-list" 
Envoyé : 2016-11-07 22:09:40
Objet : Re: [lxc-users] Something catastrophic just happened to LXC 
networking



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-beginning.pdf


Christian Tardif




-- Message d'origine --
De: "Saint Michael" 
À: "LXC users mailing-list" 
Envoyé : 2016-11-07 10:57:43
Objet : [lxc-users] Something catastrophic just happened to LXC 
networking


​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 level is:

lxc.network.type=macvlan
lxc.network.macvlan.mode=bridge
lxc.network.link=eth0
lxc.network.name = eth1
lxc.network.flags=up
lxc.network.hwaddr = mac.add.re.ss
lxc.network.ipv4 = 0.0.0.0/24

​on the host, the interface eth0 is also used by the host, but I tried 
with another interface which is UP but it has no IP, and it still does 
not allow me to reach my containers, in fact taking my business down 
since I execute a lot of stuff remotely.

Any idea?

​
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Something catastrophic just happened to LXC networking

[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-beginning.pdf


Christian Tardif




-- Message d'origine --
De: "Saint Michael" 
À: "LXC users mailing-list" 
Envoyé : 2016-11-07 10:57:43
Objet : [lxc-users] Something catastrophic just happened to LXC 
networking


​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 level is:

lxc.network.type=macvlan
lxc.network.macvlan.mode=bridge
lxc.network.link=eth0
lxc.network.name = eth1
lxc.network.flags=up
lxc.network.hwaddr = mac.add.re.ss
lxc.network.ipv4 = 0.0.0.0/24

​on the host, the interface eth0 is also used by the host, but I tried 
with another interface which is UP but it has no IP, and it still does 
not allow me to reach my containers, in fact taking my business down 
since I execute a lot of stuff remotely.

Any idea?

​
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] Wierd issue with high userID's

[Christian Tardif]

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 friday, at the office, I built two containers (Ubuntu 16.04, CentOS 
7.1) with the same kind of configuration regarding authentication; SSSD. 
And I notice that I wasn't able to log in via SSH. But one of my 
colleague was able to. We re-checke the config, just to make sure (but 
at the same time, it was impossible for this config to fail, as it is 
presented to the servers via Puppet. So the same config, and on the same 
OS level as other installs (we have numerous Ubuntu 16.04 with the same 
config, but the first one on LXD containers).


We were trying to find out what piece was missing when we discover that 
this is not just the logging that fails, but everything related to these 
high UserID's. They are coming from a calculation based on Windows SID's 
for the user, which gives a huge range of userID's, from a few thousands 
to tens, if not hundreds thousands.   So with my user, I can't set a 
permission with it, and I can't login.In fact, I don't exist with this 
user other than using "getent passwd", or "id".


What can be the cause? Something to do with namespaces, maybe?  cgroups?

We'ew in the dark. And until we can solve this, LXD containers aren't 
that helpful to us, unfortunately.


Christian Tardif

___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] How to open a ticket with LXC

[Saint Michael]

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 any connection just fine.
> Also from outside my network I can ssh into a container and ping. From the
> same network I cannot even ping a container.
>
>
>
> On Mon, Nov 7, 2016 at 1:29 PM, Judd Meinders  rockwellcollins.com> wrote:
>
>> 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
>> > lxc-users@lists.linuxcontainers.org
>> > http://lists.linuxcontainers.org/listinfo/lxc-users
>>
>> https://github.com/lxc/lxc/issues
>>
>> If you can, include steps to reproduce the issue, software versions,
>> configs, workarounds, etc.  A well formed and organized issue will get
>> more attention.
>>
>> --
>> Judd Meinders
>> ___
>> lxc-users mailing list
>> lxc-users@lists.linuxcontainers.org
>> http://lists.linuxcontainers.org/listinfo/lxc-users
>
>
>
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] How to open a ticket with LXC

[Saint Michael]

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 even ping a container.



On Mon, Nov 7, 2016 at 1:29 PM, Judd Meinders <
judd.meind...@rockwellcollins.com> wrote:

> 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
> > lxc-users@lists.linuxcontainers.org
> > http://lists.linuxcontainers.org/listinfo/lxc-users
>
> https://github.com/lxc/lxc/issues
>
> If you can, include steps to reproduce the issue, software versions,
> configs, workarounds, etc.  A well formed and organized issue will get
> more attention.
>
> --
> Judd Meinders
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] How to open a ticket with LXC

[Sean McNamara]

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 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/listinfo/lxc-users
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] How to open a ticket with LXC

[Judd Meinders]

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
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users

https://github.com/lxc/lxc/issues

If you can, include steps to reproduce the issue, software versions,
configs, workarounds, etc.  A well formed and organized issue will get
more attention.

-- 
Judd Meinders
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] How to open a ticket with LXC

[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-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] How to set a network or to empty lxd

[Vince]

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, 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 network to a container, use: lxc network attach
>
> and as a consequence I can't run apt-get in it.
> (When I ran "lxd init" I mistakenly answered "no" at the question about
> network)
>
> Can you show me
> a- how to attach a network (can't find doc)
> b- or how to empty lxd to init it a second time
>
> a) to attach a network, I tried:
> - to change the key "lxc.network.type" inside /etc/lxc/default.conf
> which was at "empty". Tried with veth (as told on irc), eth0, wlan0…
> - I tried things like "lxc network attach eth0 firstcontainer" with
> either eth0, wlan0
>
>   I shutdown lxd and try with a new container every time. No change.
>
> b) I can't run lxd init a second time because I get
> error: You have existing containers or images. lxd init requires an
> empty LXD.
> I deleted all the images I found with "lxc list", but that isn't enough.
> How can I empty lxd for real ?
>
> Thanks !
> Regards,
>
> Vincent

___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Something catastrophic just happened to LXC networking

[Saint Michael]

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:50:56:b1:8e:8a brd ff:ff:ff:ff:ff:ff
3: eth7:  mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:c9:ad brd ff:ff:ff:ff:ff:ff
4: eth0:  mtu 1500 qdisc mq state
UP mode DEFAULT group default qlen 1000
link/ether 00:50:56:b1:07:4c brd ff:ff:ff:ff:ff:ff
5: eth4:  mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:94:61 brd ff:ff:ff:ff:ff:ff
6: eth8:  mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:a6:3f brd ff:ff:ff:ff:ff:ff
7: eth1:  mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:99:ad brd ff:ff:ff:ff:ff:ff
8: eth5:  mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:83:15 brd ff:ff:ff:ff:ff:ff
9: eth9:  mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:2d:47 brd ff:ff:ff:ff:ff:ff
10: eth2:  mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:c1:ad brd ff:ff:ff:ff:ff:ff
11: eth6:  mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:50:56:b1:f2:19 brd ff:ff:ff:ff:ff:ff

On Mon, Nov 7, 2016 at 11:11 AM, Félix Archambault <
fel.archamba...@gmail.com> wrote:

> 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
> state UP mode DEFAULT group default qlen 1000
> link/ether 3c:97:0e:e7:5b:04 brd ff:ff:ff:ff:ff:ff
> 3: wlp3s0:  mtu 1500 qdisc mq state UP
> mode DORMANT group default qlen 1000
> link/ether e0:9d:31:09:96:9c brd ff:ff:ff:ff:ff:ff
> archf@it-felix-w530 ~/dotfiles>
>
>
>
> On Mon, Nov 7, 2016 at 10:57 AM, Saint Michael  wrote:
>
>> ​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 level is:
>>
>> lxc.network.type=macvlan
>> lxc.network.macvlan.mode=bridge
>> lxc.network.link=eth0
>> lxc.network.name = eth1
>> lxc.network.flags=up
>> lxc.network.hwaddr = mac.add.re.ss
>> lxc.network.ipv4 = 0.0.0.0/24
>>
>> ​on the host, the interface eth0 is also used by the host, but I tried
>> with another interface which is UP but it has no IP, and it still does not
>> allow me to reach my containers, in fact taking my business down since I
>> execute a lot of stuff remotely.
>> Any idea?
>>
>> ​
>>
>>
>> ___
>> lxc-users mailing list
>> lxc-users@lists.linuxcontainers.org
>> http://lists.linuxcontainers.org/listinfo/lxc-users
>>
>
>
>
> --
> Felix Archambault
>
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Something catastrophic just happened to LXC networking

[Félix Archambault]

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
state UP mode DEFAULT group default qlen 1000
link/ether 3c:97:0e:e7:5b:04 brd ff:ff:ff:ff:ff:ff
3: wlp3s0:  mtu 1500 qdisc mq state UP
mode DORMANT group default qlen 1000
link/ether e0:9d:31:09:96:9c brd ff:ff:ff:ff:ff:ff
archf@it-felix-w530 ~/dotfiles>



On Mon, Nov 7, 2016 at 10:57 AM, Saint Michael  wrote:

> ​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 level is:
>
> lxc.network.type=macvlan
> lxc.network.macvlan.mode=bridge
> lxc.network.link=eth0
> lxc.network.name = eth1
> lxc.network.flags=up
> lxc.network.hwaddr = mac.add.re.ss
> lxc.network.ipv4 = 0.0.0.0/24
>
> ​on the host, the interface eth0 is also used by the host, but I tried
> with another interface which is UP but it has no IP, and it still does not
> allow me to reach my containers, in fact taking my business down since I
> execute a lot of stuff remotely.
> Any idea?
>
> ​
>
>
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>



-- 
Felix Archambault
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] Something catastrophic just happened to LXC networking

[Saint Michael]

​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 level is:

lxc.network.type=macvlan
lxc.network.macvlan.mode=bridge
lxc.network.link=eth0
lxc.network.name = eth1
lxc.network.flags=up
lxc.network.hwaddr = mac.add.re.ss
lxc.network.ipv4 = 0.0.0.0/24

​on the host, the interface eth0 is also used by the host, but I tried with
another interface which is UP but it has no IP, and it still does not allow
me to reach my containers, in fact taking my business down since I execute
a lot of stuff remotely.
Any idea?

​
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] How to set a network or to empty lxd

[Vince]

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 network to a container, use: lxc network attach

and as a consequence I can't run apt-get in it.
(When I ran "lxd init" I mistakenly answered "no" at the question about
network)

Can you show me
a- how to attach a network (can't find doc)
b- or how to empty lxd to init it a second time

a) to attach a network, I tried:
- to change the key "lxc.network.type" inside /etc/lxc/default.conf
which was at "empty". Tried with veth (as told on irc), eth0, wlan0…
- I tried things like "lxc network attach eth0 firstcontainer" with
either eth0, wlan0

  I shutdown lxd and try with a new container every time. No change.

b) I can't run lxd init a second time because I get
error: You have existing containers or images. lxd init requires an
empty LXD.
I deleted all the images I found with "lxc list", but that isn't enough.
How can I empty lxd for real ?

Thanks !
Regards,

Vincent
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users