Wow, it worked! I can lxc-console into it now. I guess it had
/dev/console active but not /dev/ttys.
I don't know what is up with logging though.
On 02/07/2016 11:48 PM, Fajar A. Nugraha wrote:
> Did you try "lxc-console -t 0" ?
>
> --
> Fajar
>
> On Sun, Feb 7, 2016 at 7:37 PM, John Lewis
I have a problem with "lxc stop" command which stops the container, but
never returns.
It used to work some time ago (not sure when exactly it stopped
working).
# dpkg -l|grep lxd
ii lxd
2.0.0~beta1-0ubuntu4~ubuntu14.04.1~ppa1 amd64Container
hy
yea, as suggested by Luis, set it beforehand so you know what connects
where.
if you are using the default stuff then on host run run :
ethtool -S
Which will give you the ifindex of veth peer inside container which can be
matched using :
lxc-attach -n -s NETWORK -- /sbin/ip link show eth0
Yo
Hi,
In /var/lib/lxc/[container]/config, use lxc.network.veth.pair = [name] to
assign a particular name for a veth.
Regards,
2016-02-08 19:36 GMT-05:00 tapczan :
> Hello
>
> Is there any way to determine which vethXXX interface is connected to
> a particular running LXC container?
>
> Or eve
Quoting Alain St-Denis (al...@zenfolie.org):
> Hi,
>
> I was able to work around the issue. There appear to be two reasons why
> the polkit authentication agent can't find a user session. First, no
> session can be created if /dev/tty0 doesn't exist as per this code in
> systemd-204/src/login/logi
Hello
Is there any way to determine which vethXXX interface is connected to
a particular running LXC container?
Or even more precisely, which vethXXX interface is connected to a
particular interface inside LXC container, eg.:
vethL6OCF0 <-> container1: eth0
vethGMSWTE <-> container1: eth1
vethME
Hi,
I was able to work around the issue. There appear to be two reasons why
the polkit authentication agent can't find a user session. First, no
session can be created if /dev/tty0 doesn't exist as per this code in
systemd-204/src/login/logind.c manager_connect_console:
if (access("/dev/tty0", F_