Re: /usr/sbin/reboot: disabled in systemd-nspawn container
On Sat, 04 Sep 2021 14:46:21 -0400
The Wanderer <wanderer@fastmail.fm> wrote:
> On 2021-09-04 at 13:20, Greg Wooledge wrote:
>
> > On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote:
> >
> >> Greg Wooledge [2021-09-04 11:35:25] wrote:
> >> > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp007@caiway.net wrote:
> >> >> # file /sbin/reboot
>
> Based on what I read of the thread, that package is
> progress-linux-container.
>
> $ apt-cache policy progress-linux-container
> progress-linux-container:
> Installed: (none)
> Candidate: 20210101-2
> Version table:
> 20210101-2 900
> 800 http://ftp.us.debian.org/debian stable/main amd64 Packages
> 800 http://ftp.us.debian.org/debian stable/main i386 Packages
> 900 http://ftp.us.debian.org/debian testing/main amd64
> Packages 900 http://ftp.us.debian.org/debian testing/main i386
> Packages
>
> progress-linux-container is a package in Debian, and at least at a
> glance, is apparently meant for installing on a Debian system. (Or
> else it made it from the downstream distribution into upstream Debian
> by mistake, somehow.)
>
> It's just not meant for installing on a host system; it's meant for
> installing only inside a container.
>
> What resulted in it being installed in the OP's case is unclear (the
> OP has said he doesn't know), but at least at a glance it doesn't
> look like this is a case of mixing different operating systems,
> unless I'm misunderstanding what you mean by that.
>
Thw Wanderer, you are absolutely right
our posts may have crossed
the case is solved
see above
# apt remove progress-linux-container
solved the issue
and in addition,
I must have installed by hand, in the wrong place
in OS not inside container
my bad
glad it is cleared
thanks
sp007
Reply to: