Home | Devuan | Git | Forum | Packages | Popcon

Download

Devuan bug report logs - #442
bash: cannot use job control in an unprivileged LXC container

Package: bash; Severity: minor; Reported by: Ryutaroh Matsumoto <[email protected]>; dated Fri, 8 May 2020 08:33:01 UTC; Maintainer for bash is (unknown).

Message received at [email protected]:

Date: Sun, 10 May 2020 09:52:31 +0900 (JST)
Message-Id: <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: bash: cannot use job control in an unprivileged LXC container
From: Ryutaroh Matsumoto <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I verified that #442 bash: cannot use job control in an unprivileged LXC container
is reproducible when
Host Linux = Devuan Beowulf
Guest Linux = Devuan Beowulf
(after addressing #445).

On the other hand, I have never seen this issue when a container guest is not Devuan...
Ryutaroh

Acknowledgement sent to Ryutaroh Matsumoto <[email protected]>:
Extra info received and forwarded to list. Copy sent to [email protected]. Full text available.

Information forwarded to [email protected], [email protected]:
bug#442; Package bash. Full text available.

Message received at [email protected]:

Date: Fri, 08 May 2020 20:00:00 +0900 (JST)
Message-Id: <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: bash: cannot use job control in an unprivileged LXC container
From: Ryutaroh Matsumoto <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> The usual quoted workaround for this sysmptom is using setsid(1) so that
> the  process is a session leader. However, I don't have any experience with lxc
> to know if that is possible or relevant in this case.

"setsid bash" did not work around this symptom...
On the other hand, logging in by "lxc-attach -n devuan" as root
does not cause this symptom, so it is another workaround...

Best regards, Ryutaroh

Acknowledgement sent to Ryutaroh Matsumoto <[email protected]>:
Extra info received and forwarded to list. Copy sent to [email protected]. Full text available.

Information forwarded to [email protected], [email protected]:
bug#442; Package bash. Full text available.

Message received at [email protected]:

Received: (at 442) by bugs.devuan.org; 8 May 2020 11:00:02 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Fri, 08 May 2020 11:00:02 +0000 (UTC)
Received: from mail002.nap.gsic.titech.ac.jp (mail002.nap.gsic.titech.ac.jp [131.112.13.102])
	by vm6.ganeti.dyne.org (Postfix) with SMTP id E828BF604B7
	for <[email protected]>; Fri,  8 May 2020 12:54:33 +0200 (CEST)
Received: from 172.22.40.202
	by mail002.nap.gsic.titech.ac.jp with Mail2000 ESMTP Server V7.00(2646:0:AUTH_RELAY)
	(envelope-from <[email protected]>); Fri, 08 May 2020 19:54:32 +0900 (JST)
Received: from mail002.nap.gsic.titech.ac.jp (mail002.nap.gsic.titech.ac.jp [131.112.13.102])
	by drweb05.nap.gsic.titech.ac.jp (Postfix) with SMTP id 9938716B27;
	Fri,  8 May 2020 19:54:32 +0900 (JST)
Received: from 126.255.18.103
	by mail002.nap.gsic.titech.ac.jp with Mail2000 ESMTPA Server V7.00(2636:0:AUTH_LOGIN)
	(envelope-from <[email protected]>); Fri, 08 May 2020 19:54:30 +0900 (JST)
Date: Fri, 08 May 2020 19:54:29 +0900 (JST)
Message-Id: <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: bash: cannot use job control in an unprivileged LXC container
From: Ryutaroh Matsumoto <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Hi Mark,

>> I cannot test sysvinit on Buster, because Debian Buster does not have
>> the sysvinit-core package!!!!!
> I think it does:
(deleted)
> But no matter, I was just trying to narrow down possibilities.

Sorry, you are right and I was wrong.
Actually, apt-get install sysvinit-core reproduces the same symptom
with Debian Buster with sysvinit-core.

Best regards, Ryutaroh

Acknowledgement sent to Ryutaroh Matsumoto <[email protected]>:
Extra info received and forwarded to list. Copy sent to [email protected]. Full text available.

Information forwarded to [email protected], [email protected]:
bug#442; Package bash. Full text available.

Message received at [email protected]:

Received: (at 442) by bugs.devuan.org; 8 May 2020 11:00:02 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Fri, 08 May 2020 11:00:02 +0000 (UTC)
Received: from mx.hindley.org.uk (mohindley.plus.com [81.174.245.179])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id BF467F60B24
	for <[email protected]>; Fri,  8 May 2020 12:51:33 +0200 (CEST)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1jX0bM-0003SV-04; Fri, 08 May 2020 11:51:32 +0100
Received: (nullmailer pid 9729 invoked by uid 1000);
	Fri, 08 May 2020 10:51:31 -0000
Date: Fri, 8 May 2020 11:51:31 +0100
From: Mark Hindley <[email protected]>
To: Ryutaroh Matsumoto <[email protected]>
Cc: [email protected]
Subject: Re: bash: cannot use job control in an unprivileged LXC container
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
 <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=disabled
	version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

On Fri, May 08, 2020 at 07:43:50PM +0900, Ryutaroh Matsumoto wrote:
> Hi Mark,
> 
> > Is that not seen on  Debian running systemd or sysvinit?
> 
> I do not see this symptom with
> 
> Host Linux = Debian Bullseye (lxc version 4.0.2 in Debian experimental)
> Guest Linux = Debian Buster runnning systemd-sysv (bash package version is 5.0-4).
> 
> I cannot test sysvinit on Buster, because Debian Buster does not have
> the sysvinit-core package!!!!!

I think it does:

sysvinit-core | 2.88dsf-59    | oldoldstable | amd64, armel, armhf, i386
sysvinit-core | 2.88dsf-59.9  | oldstable    | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
sysvinit-core | 2.93-8        | stable       | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
sysvinit-core | 2.96-3        | testing      | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
sysvinit-core | 2.96-3        | unstable     | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x

But no matter, I was just trying to narrow down possibilities.

> 
> > This message is usually seen when there is no tty allocated. Are you logging in
> > from a text terminal or x terminal?
> 
> "lxc-start -F -n devuan" was started from tty3 (text).

The usual quoted workaround for this sysmptom is using setsid(1) so that
the  process is a session leader. However, I don't have any experience with lxc
to know if that is possible or relevant in this case.

Best wishes

Mark

Acknowledgement sent to Mark Hindley <[email protected]>:
Extra info received and forwarded to list. Copy sent to [email protected]. Full text available.

Information forwarded to [email protected], [email protected]:
bug#442; Package bash. Full text available.

Message received at [email protected]:

Received: (at 442) by bugs.devuan.org; 8 May 2020 10:50:04 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Fri, 08 May 2020 10:50:04 +0000 (UTC)
Received: from mail002.nap.gsic.titech.ac.jp (mail002.nap.gsic.titech.ac.jp [131.112.13.102])
	by vm6.ganeti.dyne.org (Postfix) with SMTP id 5F2E7F609E9
	for <[email protected]>; Fri,  8 May 2020 12:43:53 +0200 (CEST)
Received: from 172.22.40.205
	by mail002.nap.gsic.titech.ac.jp with Mail2000 ESMTP Server V7.00(2643:0:AUTH_RELAY)
	(envelope-from <[email protected]>); Fri, 08 May 2020 19:43:51 +0900 (JST)
Received: from mail004.nap.gsic.titech.ac.jp (mail004.nap.gsic.titech.ac.jp [131.112.13.104])
	by drweb08.nap.gsic.titech.ac.jp (Postfix) with SMTP id 368B2EB;
	Fri,  8 May 2020 19:43:51 +0900 (JST)
Received: from 126.255.18.103
	by mail004.nap.gsic.titech.ac.jp with Mail2000 ESMTPA Server V7.00(2772:0:AUTH_LOGIN)
	(envelope-from <[email protected]>); Fri, 08 May 2020 19:43:50 +0900 (JST)
Date: Fri, 08 May 2020 19:43:50 +0900 (JST)
Message-Id: <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: bash: cannot use job control in an unprivileged LXC container
From: Ryutaroh Matsumoto <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Hi Mark,

> Is that not seen on  Debian running systemd or sysvinit?

I do not see this symptom with

Host Linux = Debian Bullseye (lxc version 4.0.2 in Debian experimental)
Guest Linux = Debian Buster runnning systemd-sysv (bash package version is 5.0-4).

I cannot test sysvinit on Buster, because Debian Buster does not have
the sysvinit-core package!!!!!

> This message is usually seen when there is no tty allocated. Are you logging in
> from a text terminal or x terminal?

"lxc-start -F -n devuan" was started from tty3 (text).
I did not test GUI terminal, as I don't have it on Debian Bullseye.

Best regards, Ryutaroh

Acknowledgement sent to Ryutaroh Matsumoto <[email protected]>:
Extra info received and forwarded to list. Copy sent to [email protected]. Full text available.

Information forwarded to [email protected], [email protected]:
bug#442; Package bash. Full text available.

Message received at [email protected]:

Received: (at 442) by bugs.devuan.org; 8 May 2020 10:10:02 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Fri, 08 May 2020 10:10:02 +0000 (UTC)
Received: from mx.hindley.org.uk (mohindley.plus.com [81.174.245.179])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id B3D83F606E2
	for <[email protected]>; Fri,  8 May 2020 11:57:16 +0200 (CEST)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1jWzkm-00031c-MC; Fri, 08 May 2020 10:57:12 +0100
Received: (nullmailer pid 8802 invoked by uid 1000);
	Fri, 08 May 2020 09:57:12 -0000
Date: Fri, 8 May 2020 10:57:11 +0100
From: Mark Hindley <[email protected]>
To: [email protected], Ryutaroh Matsumoto <[email protected]>
Subject: Re: bash: cannot use job control in an unprivileged LXC container
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
X-Debbugs-No-Ack: No Thanks
X-IMAPbase: 1220827534 0000000216
X-UID: 216
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Spam-Status: No, score=0.0 required=5.0 tests=FAKE_REPLY_C,SPF_PASS
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Ryutaroh,

Thanks.

On Fri, 08 May 2020 17:08:10 +0900 (JST) Ryutaroh Matsumoto <[email protected]> wrote:
> Package: bash
> Version: 5.0-4
> Severity: minor
> 
> Dear Maintainer,
> 
> I made an LXC unprivileged container of Devuan on Debian Bullseye by
> mmdebstrap --mode=unshare --components="main contrib non-free" --variant=standard beowulf /home/ryutaroh/.local/share/lxc/devuan/rootfs http://deb.devuan.org/merged
> 
> "Unprivileged" means that it is started by a non-root user (on host Linux).
> 
> The Devuan container works almost fine, but I experienced a minor problem.
> When I login from /dev/console by "lxc-start -F -n devuan",
> I got the error message from /bin/bash as
> 
> -bash: cannot set terminal process group (709): Inappropriate ioctl for device
> -bash: no job control in this shell

This message is usually seen when there is no tty allocated. Are you logging in
from a text terminal or x terminal?

> I do not see the above problem when Devuan is started in
> a privileged LXC container.
> I do not see the above problem in recent releases of Debian or Ubuntu running
> in LXC containers, neither, so it seems Devuan-specific.

Is that not seen on  Debian running systemd or sysvinit?

Thanks

Mark

Information forwarded to [email protected], [email protected]:
bug#442; Package bash. Full text available.

Message received at [email protected]:

Received: (at submit) by bugs.devuan.org; 8 May 2020 08:20:03 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Fri, 08 May 2020 08:20:03 +0000 (UTC)
Received: from mail001.nap.gsic.titech.ac.jp (mail001.nap.gsic.titech.ac.jp [131.112.13.101])
	by vm6.ganeti.dyne.org (Postfix) with SMTP id B1306F604C2
	for <[email protected]>; Fri,  8 May 2020 10:08:20 +0200 (CEST)
Received: from 172.22.40.202
	by mail001.nap.gsic.titech.ac.jp with Mail2000 ESMTP Server V7.00(2599:0:AUTH_RELAY)
	(envelope-from <[email protected]>); Fri, 08 May 2020 17:08:17 +0900 (JST)
Received: from mail004.nap.gsic.titech.ac.jp (mail004.nap.gsic.titech.ac.jp [131.112.13.104])
	by drweb05.nap.gsic.titech.ac.jp (Postfix) with SMTP id 2B01911D40
	for <[email protected]>; Fri,  8 May 2020 17:08:17 +0900 (JST)
Received: from 131.112.36.198
	by mail004.nap.gsic.titech.ac.jp with Mail2000 ESMTPA Server V7.00(2784:0:AUTH_LOGIN)
	(envelope-from <[email protected]>); Fri, 08 May 2020 17:08:16 +0900 (JST)
Date: Fri, 08 May 2020 17:08:10 +0900 (JST)
Message-Id: <[email protected]>
To: Devuan Bug Tracking System <[email protected]>
Subject: bash: cannot use job control in an unprivileged LXC container
From: Ryutaroh Matsumoto <[email protected]>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Package: bash
Version: 5.0-4
Severity: minor

Dear Maintainer,

I made an LXC unprivileged container of Devuan on Debian Bullseye by
mmdebstrap --mode=unshare --components="main contrib non-free" --variant=standard beowulf /home/ryutaroh/.local/share/lxc/devuan/rootfs http://deb.devuan.org/merged

"Unprivileged" means that it is started by a non-root user (on host Linux).

The Devuan container works almost fine, but I experienced a minor problem.
When I login from /dev/console by "lxc-start -F -n devuan",
I got the error message from /bin/bash as

-bash: cannot set terminal process group (709): Inappropriate ioctl for device
-bash: no job control in this shell

I do not see the above problem when Devuan is started in
a privileged LXC container.

I do not see the above problem in recent releases of Debian or Ubuntu running
in LXC containers, neither, so it seems Devuan-specific.

I guess that the above problem may occur in a Devuan container on Devuan host,
so it should be reproducible only in Devuan (without use of Debian or Ubuntu).

Best regards, Ryutaroh Matsumoto


-- System Information:
Architecture: x86_64

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages bash depends on:
ii  base-files   10.3+devuan3.4
ii  debianutils  4.8.6.1
ii  libc6        2.28-10
ii  libtinfo6    6.1+20181013-2+deb10u2

Versions of packages bash recommends:
ii  bash-completion  1:2.8-6

Versions of packages bash suggests:
pn  bash-doc  <none>

-- no debconf information

Acknowledgement sent to Ryutaroh Matsumoto <[email protected]>:
New bug report received and forwarded. Copy sent to [email protected]. Full text available.

Report forwarded to [email protected], [email protected]:
bug#442; Package bash. Full text available.

Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.

Devuan Bugs Owner <[email protected]>.
Last modified: Sat, 30 Nov 2024 22:39:01 UTC