Stéphane was helpfully pointing you in the direction of where the problem
probably lies.  Don't read it as "your problem isn't important so I'm
closing it", read it as "your problem sounds like it could be x or y."

github.com/lxc/lxc tracks upstream lxc.  This is independent of Ubuntu.
If you want to file an ubuntu bug, go to
https://launchpad.net/ubuntu/+source/lxc or
https://launchpad.net/ubuntu/+source/linux for the kernel, and hit
'Report a bug' on the right.  (Or if you pay for support go through your
support channel)

github.com/lxc/lxc is also an independent volunteer project, so the entitlement
in this message is unwarranted.  If I show up to help move your couch in my
free time, you can't complain that I didn't paint your walls.  The message
closing your issue was a very polite, respectful, and helpful one.

I understand that as a user you don't really want to have to care about
who's providing what software, but everyone will be able to do their jobs
much better if they can focus on what they focus on.

-serge

Quoting Saint Michael (vene...@gmail.com):
> 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 <vene...@gmail.com> wrote:
> 
> > I already open a ticket
> > https://github.com/lxc/lxc/issues/1284
> >
> > On Mon, Nov 7, 2016 at 1:43 PM, Saint Michael <vene...@gmail.com> 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 <vene...@gmail.com>
> >>> 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

Reply via email to