[systemd-devel] Antw: [EXT] Re: Q: Start network in chroot?

[Michał Zegan]

W dniu 13.06.2022 o 16:34, Colin Guthrie pisze:
>
> Ulrich Windl wrote on 13/06/2022 14:42:
>>>>> Colin Guthrie <gmane at colin.guthr.ie> schrieb am 13.06.2022 um 
>>>>> 14:58 in
>> Nachricht <t87c9t$lon$1 at ciao.gmane.io>:
>>> Ulrich Windl wrote on 13/06/2022 09:09:
>>>> Hi!
>>>>
>>>> Two questions:
>>>> 1) Why can't I use "systemctl start network" in a chroot 
>>>> environment (e.g.
>>> mounting the system from a rescue medium to fix a defective kernel)? 
>>> When I
>>> try I get: "Running in chroot, ignoring command 'start'"
>>>> 2) How can I start the network using systemd?
>>>
>>> You may wish to consider "booting" the container rather than just 
>>> chrooting.
>>
>> No container involved; an unbootable system instead, and I'd like to 
>> have networking available for repair.
>> So obviously I cannot boot. Without systemd it wouldn't be a problem.

in theory you have unshare in mos environments. you might not have 
access to nspawn, but you can unshare. I have used raw namespaces 
previously, although mostly mount ns, not network ns.

also this is uncommon that you cannot configure the network before 
chrooting, as in at host side, then just copy or bindmount resolv.conf 
and have it working in chroot.

>
> So you're not running an init system but you want the (not-running) 
> init system to run something for you?
>
> If you're wanting to repair a system, and you need networking then 
> bring up the network in the repair image before chrooting surely? 
> (i.e. what Mantas said)
>
> If you want to run the network inside the (broken) system you're 
> trying to repair, then just run the networking scripts or program 
> manually. i.e. run whatever /etc/init.d/network says or whatever 
> ExecStart= says in /usr/lib/systemd/network.service says (paths may 
> vary).
>
> There will be loads of other stuff that the init system does that 
> won't be in place (e.g. tmpfiles, etc.) which you may or may not need 
> to setup manually too, but you can likely get it running.
>
> > Without systemd it wouldn't be a problem.
>
> Sure when "init" was just a bundle of scripts, you could run one of 
> the scripts it runs and hope for the best. You can generally still do 
> that, but just don't expect asking a non-running program to do it for 
> you to work!
>
> Col
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0xE6516A8A8E25955D.asc
Type: application/pgp-keys
Size: 10971 bytes
Desc: OpenPGP public key
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20220613/33ba053f/attachment-0001.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20220613/33ba053f/attachment-0001.sig>