Re: [lxc-users] TTY issue

[Saint Michael]

I use full privileged containers, since this is just a mechanism to move
around higly complex installations.
In my business there is one host and one container per box, which uses up
all resources available.
What you are saying, basically, is the root-privileged containers is not
support by LXC, since a container does hijack the host's TTY.
Any confirmation of this?
I cannot believe this is impossible to solve.


On Wed, Nov 15, 2017 at 10:19 PM, Fajar A. Nugraha  wrote:

> On Thu, Nov 16, 2017 at 10:04 AM, Saint Michael  wrote:
>
>> I did apply all suggested solutions that you found googling. None works.
>> I do not use LXD, just plain LXC.
>> lxc-start --version
>> 2.0.9
>> lsb_release -a
>> No LSB modules are available.
>> Distributor ID: Ubuntu
>> Description:Ubuntu 16.04.3 LTS
>> Release:16.04
>> Codename:   xenial
>>
>>
>>
> Short version: use root-owned unprivileged containers.
> If you don't know how to do that (or think it's too troublesome to
> configure with lxc), then just use LXD (which use root-owned unprivileged
> containers by default).
>
> --
> Fajar
>
> ___
> 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] TTY issue

[Fajar A. Nugraha]

On Thu, Nov 16, 2017 at 10:04 AM, Saint Michael  wrote:

> I did apply all suggested solutions that you found googling. None works.
> I do not use LXD, just plain LXC.
> lxc-start --version
> 2.0.9
> lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:Ubuntu 16.04.3 LTS
> Release:16.04
> Codename:   xenial
>
>
>
Short version: use root-owned unprivileged containers.
If you don't know how to do that (or think it's too troublesome to
configure with lxc), then just use LXD (which use root-owned unprivileged
containers by default).

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

Re: [lxc-users] TTY issue

[Saint Michael]

I did apply all suggested solutions that you found googling. None works.
I do not use LXD, just plain LXC.
lxc-start --version
2.0.9
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial


On Wed, Nov 15, 2017 at 9:42 PM, Andrey Repin  wrote:

> Greetings, Saint Michael!
>
> > My host is Ubuntu LTS
>
> Which "LTS"?…
>
> > and my container is Centos 7.
>
> And what you are using for containers?
> LXC? LXD? Which version?
>
> > Every time the server boots, the container takes over the tty0 of the
> > server, Ubuntu, and freezes the interface.
> > The only way to log to the server itsef is to press ALT+F2 and use the
> second tty.
> > I tried to remove tty0 on the guest, and also this (on the guest)
> > systemctl stop getty@tty1.service; systemctl mask getty@tty1.service
> > but the issue continues. Any idea how can I block any container from
> > hijacking te host's tty?
>
> Your report lacking a lot of critical information. And it doesn't look like
> you did a google on your problem either. I was able to easily find a
> number of
> references to similar issues, and they all contain suggested solutions,
> unfortunately, without a call back from the original poster(s) about
> success/failure of applying them.
>
>
> --
> With best regards,
> Andrey Repin
> Thursday, November 16, 2017 05:37:58
>
> Sorry for my terrible english...
> ___
> 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] TTY issue

[Andrey Repin]

Greetings, Saint Michael!

> My host is Ubuntu LTS

Which "LTS"?…

> and my container is Centos 7.

And what you are using for containers?
LXC? LXD? Which version?

> Every time the server boots, the container takes over the tty0 of the
> server, Ubuntu, and freezes the interface.
> The only way to log to the server itsef is to press ALT+F2 and use the second 
> tty.
> I tried to remove tty0 on the guest, and also this (on the guest)
> systemctl stop getty@tty1.service; systemctl mask getty@tty1.service
> but the issue continues. Any idea how can I block any container from
> hijacking te host's tty?

Your report lacking a lot of critical information. And it doesn't look like
you did a google on your problem either. I was able to easily find a number of
references to similar issues, and they all contain suggested solutions,
unfortunately, without a call back from the original poster(s) about
success/failure of applying them.


-- 
With best regards,
Andrey Repin
Thursday, November 16, 2017 05:37:58

Sorry for my terrible english...
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] TTY issue

[Saint Michael]

My host is Ubuntu LTS and my container is Centos 7. Every time the server
boots, the container takes over the tty0 of the server, Ubuntu, and freezes
the interface. The only way to log to the server itsef is to press ALT+F2
and use the second tty. I tried to remobve tty0 on the gest, and also this
(on the guest)
systemctl stop getty@tty1.service; systemctl mask getty@tty1.service
but the issue continues. Any idea how can I block any container from
hijacking te host's tty?
Philip
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users