On Wed, Nov 9, 2016 at 12:37 PM, Saint Michael <vene...@gmail.com> wrote:
> I understand how you see it. > Maybe it was my mistake to get on the LXC bandwagon two years ago. I > should not bet my business on a non-commercial, unsupported software. > You do realise that if you purchase support package from canonicall for ubuntu, it should also include commercial support for lxc/lxd on ubuntu? > Now it is too late. > > I read your ticket, and there's not much info to go on there. With the limited amount of info, the obvious thing to check would be your configuration. If you still have the problem, I suggest you create a NEW thread on list, with the appropriate subject, and include these info: - what version of distro and lxc are you running - how did you install lxc package (e.g. ubuntu's default repo, ppa self compiled) - how did you setup your network (e.g. creating a manual bridge with the host physical interface eth0, or default lxcbr0 bridge, or proxyarp, etc) - do you have firewall active on your host (e.g. output of "iptables -nL" or similar) - lxc config file for the problematic container (you can mask sensitive info if you like) -- Fajar
_______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
