all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, 34211@debbugs.gnu.org, help-guix@gnu.org
Subject: bug#34211: error running container: mingetty cannot find ttys
Date: Tue, 12 Feb 2019 11:25:19 +0100	[thread overview]
Message-ID: <8736otfgmo.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <87zhr2q862.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2397 bytes --]

Hi Ludo'

thank you for looking into this issue!

Ludovic Courtès <ludo@gnu.org> writes:

[...]

> I also get this behavior.

OK, so this is deterministic now :-)

> What happens is that the /dev/ttyN nodes do not exist (understandably),
> and thus the ‘console-font-ttyN’ Shepherd services fail to start, and
> get restarted, indefinitely.

actually they do fail but they are not respawned, the services that get
respawned are term-tty[1..6]

> The container is working as expected though.  If you find the PID of the
> container’s ‘shepherd’ process (its PID 1, which obviously has a
> different PID outside the container), then you can do:
>
>   guix container exec NNN /bin/sh

I have to use "sudo" to be able to start and "guix container exec" a
shell in it (I mean: sudo guix container exec...)

I used that command in another terminal so I could see the console
messages from the container

> where NNN is that PID of that ‘shepherd’ process (I use ‘pstree’ to find
> the PID… not very convenient.)

oh yes! I did not realized that my container was there waiting for me
:-)
...I also did not realized thet the container is started as a foreground
process, so we nees to background

I used pstree too, we need a better way to interact with a container (by
name and not by PID); sorry but I still cannot help here, my Guile
proficency is still too low; anyway this is tangent to this bug

> In that shell, you can do:

[...]

> So in that sense everything is working “as expected.”

yes, I see: I stopped term-tty[1..6] and the failure messages disappeared

> Now, it would make more sense to simply remove those ‘console-font-ttyN’
> services in a container and everything that depends on them.

as pointed above the faining services are term-tty[1..6],
console-font-tty[1..6] fails but do not get respawned do they are not
the real issue

> Not sure if we should do that automatically.

I'll try to remove term-tty[1..6] manually from services declaration, if
I manage to "manually" solve this I'll report here

> Thoughts?

since mingetty does not make sense in a container I'd remove
term-tty[1..6] (and console-font-tty[1..6]) automatically and by default
when we create a container via "guix system container..."

Thanks!
Giovanni

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-02-12 10:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 17:46 error running container: mingetty cannot find ttys Giovanni Biscuolo
2019-01-26 19:21 ` Efraim Flashner
2019-01-27 14:49   ` Giovanni Biscuolo
2019-01-27 16:15     ` Efraim Flashner
2019-02-06 12:16   ` bug#34211: " Giovanni Biscuolo
2019-02-06 12:16   ` Giovanni Biscuolo
2019-02-11 22:20     ` bug#34211: " Ludovic Courtès
2019-02-12 10:25       ` Giovanni Biscuolo [this message]
2019-02-13 17:19         ` Giovanni Biscuolo
2019-02-14 20:08           ` Arun Isaac
2019-02-15  8:57             ` Giovanni Biscuolo
2019-02-15 10:39               ` Arun Isaac
2019-02-15 10:39               ` Arun Isaac
2019-02-15 11:34                 ` Giovanni Biscuolo
2019-02-15 11:34                 ` Giovanni Biscuolo
2019-02-15 12:00                   ` Arun Isaac
2019-02-15 12:00                   ` Arun Isaac
2019-03-13 22:13                     ` Ludovic Courtès
2019-02-15  8:57             ` Giovanni Biscuolo
2019-02-13 17:19         ` Giovanni Biscuolo
2019-02-11 22:20     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8736otfgmo.fsf@roquette.mug.biscuolo.net \
    --to=g@xelera.eu \
    --cc=34211@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.