Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #239690
| From | "sp007@caiway.net" <sp007@caiway.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: /usr/sbin/reboot: disabled in systemd-nspawn container |
| Date | 2021-09-04 22:40 +0200 |
| Message-ID | <CTKCd-7We-7@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <CTFsS-4Hd-7@gated-at.bofh.it> <CTGfg-4YZ-11@gated-at.bofh.it> <CTHuF-61n-1@gated-at.bofh.it> <CTHO1-693-1@gated-at.bofh.it> <CTJd8-7ao-5@gated-at.bofh.it> |
| Organization | amd |
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
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
/usr/sbin/reboot: disabled in systemd-nspawn container "sp007@caiway.net" <sp007@caiway.net> - 2021-09-04 15:00 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container Reco <recoverym4n@enotuniq.net> - 2021-09-04 16:10 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container "sp007@caiway.net" <sp007@caiway.net> - 2021-09-04 17:10 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container Reco <recoverym4n@enotuniq.net> - 2021-09-04 17:40 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container Greg Wooledge <greg@wooledge.org> - 2021-09-04 18:00 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container Stefan Monnier <monnier@iro.umontreal.ca> - 2021-09-04 19:20 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container Greg Wooledge <greg@wooledge.org> - 2021-09-04 19:40 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container The Wanderer <wanderer@fastmail.fm> - 2021-09-04 21:10 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container "sp007@caiway.net" <sp007@caiway.net> - 2021-09-04 22:40 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container "sp007@caiway.net" <sp007@caiway.net> - 2021-09-04 17:40 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container SOLVED "sp007@caiway.net" <sp007@caiway.net> - 2021-09-04 18:00 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container SOLVED Andrei POPESCU <andreimpopescu@gmail.com> - 2021-09-12 09:50 +0200
csiph-web