Re: /usr/sbin/reboot: disabled in systemd-nspawn container

["sp007@caiway.net" <sp007@caiway.net>]

On Sat, 4 Sep 2021 16:42:45 +0300
Reco <recoverym4n@enotuniq.net> wrote:

> 	Hi.

> /bin/systemd reboot
> 
> And, what about these:
> 
> ls -al /sbin/reboot
> file /sbin/reboot
> 
> Reco
> 

the commands poweroff and reboot are textfiles.
I have no idea

# mcedit /sbin/reboot:
#!/bin/sh

echo "${0}: disabled in systemd-nspawn container"

if [ -e /etc/open-infrastructure/container/shutdown.txt ]
then
        cat /etc/open-infrastructure/container/shutdown.txt
elif [ -e /usr/share/open-infrastructure/container/shutdown.txt ]
then
        cat /usr/share/open-infrastructure/container/shutdown.txt
fi

exit 1

#eof

# mcedit /sbin/poweroff:
#!/bin/sh

echo "${0}: disabled in systemd-nspawn container"

if [ -e /etc/open-infrastructure/container/shutdown.txt ]
then
        cat /etc/open-infrastructure/container/shutdown.txt
elif [ -e /usr/share/open-infrastructure/container/shutdown.txt ]
then
        cat /usr/share/open-infrastructure/container/shutdown.txt
fi

exit 1



# cat /usr/share/open-infrastructure/container/shutdown.txt

Linux container share the kernel of the host system they are running on,
there is no need to reboot just the container.

However, please contact your system administrator to reboot this
container from the host system.

So the reason is found, now I have to find out who/what take over these
basic commands

I have no packages with open-infrastructure installed

tia