Hello! Started the container with trace and even the attaching console. --- start-log --- lxc-start tc 20190529154624.524 TRACE start - start.c:lxc_recv_ttys_from_child:1477 - Received pty with master fd 27 and slave fd 28 from parent lxc-start tc 20190529154624.524 TRACE start - start.c:lxc_recv_ttys_from_child:1483 - Received 4 ttys from child lxc-start tc 20190529154624.524 NOTICE start - start.c:post_start:2048 - Started "/sbin/init" with pid "1499" lxc-start tc 20190529154624.524 TRACE start - start.c:lxc_serve_state_socket_pair:536 - Sent container state "RUNNING" to 5 lxc-start tc 20190529154624.524 TRACE start - start.c:lxc_serve_state_clients:466 - Set container state to RUNNING lxc-start tc 20190529154624.524 TRACE start - start.c:lxc_serve_state_clients:469 - No state clients registered lxc-start tc 20190529154624.524 DEBUG lxccontainer - lxccontainer.c:wait_on_daemonized_start:830 - First child 1495 exited lxc-start tc 20190529154624.524 TRACE lxccontainer - lxccontainer.c:wait_on_daemonized_start:846 - Container is in "RUNNING" state lxc-start tc 20190529154624.524 TRACE start - start.c:lxc_poll:622 - Mainloop is ready lxc-start tc 20190529154624.524 NOTICE start - start.c:signal_handler:430 - Received 17 from pid 1497 instead of container init 1499 --- --- console log --- lxc-console tc 20190529154800.937 DEBUG commands - commands.c:lxc_cmd_rsp_recv:165 - Response data length for command "get_state" is 0 lxc-console tc 20190529154800.937 DEBUG commands - commands.c:lxc_cmd_get_state:585 - Container "tc" is in "RUNNING" state lxc-console tc 20190529154800.937 TRACE commands - commands.c:lxc_cmd_rsp_recv:139 - Command "console" received response lxc-console tc 20190529154800.937 DEBUG commands - commands.c:lxc_cmd_rsp_recv:165 - Response data length for command "console" is 0 lxc-console tc 20190529154800.937 INFO commands - commands.c:lxc_cmd_console:744 - Alloced fd 5 for tty 1 via socket 4 lxc-console tc 20190529154800.937 TRACE terminal - terminal.c:lxc_console:1060 - Process is already group leader lxc-console tc 20190529154800.937 DEBUG terminal - terminal.c:lxc_terminal_signal_init:192 - Created signal fd 6 lxc-console tc 20190529154800.937 DEBUG terminal - terminal.c:lxc_terminal_winsz:90 - Set window size to 132 columns and 50 rows lxc-console tc 20190529154800.937 TRACE commands - commands.c:lxc_cmd_rsp_recv:139 - Command "terminal_winch" received response lxc-console tc 20190529154800.937 DEBUG commands - commands.c:lxc_cmd_rsp_recv:165 - Response data length for command "terminal_winch" is 0 --- This is on host Buster with container Stretch. This tells me, the comminication is failing.
Regards, Manfred > -----Original Message----- > From: lxc-users [mailto:lxc-users-boun...@lists.linuxcontainers.org] > On Behalf Of web...@manfbraun.de > Sent: Wednesday, May 29, 2019 4:33 PM > To: lxc-users@lists.linuxcontainers.org > Subject: [lxc-users] LXC-3.1 - console disfunctional > > Hello! > > I am just trying debian buster and > found LCX -3.1 and gave it a try. > After making the networking configuration, > I started the container and tried to login > via console > > >lxc-console [-n] rxdptest1 > > A hello message appears, but that's all! > No logon prompt at all, even not pressing enter several times. > > I can use attach, but this different. > Astoundingly, after connecting via Putty from > Windows, the usual curor keys to edit [1]the commandline, > don't work. I think, the has a relationship. > > Any help would be great! > > Thanks so far, > Manfred > > [added console-data, reconfigured keyboard-layout without changes] > [Debian buster, kernel, 4.19, LXC-3.1] > > > > _______________________________________________ > 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
