Lines Matching refs:on

14 when systemd is used inside of an OS container. If you work on a container
26    read-only (the latter via e.g. a read-only bind mount on itself) in order
35    so on. If you do that, make sure to mark `/sys/` read-only, as that
46    or `/dev/stdout`, as systemd will do that on its own. Make sure to set up a
47    `BPF_PROG_TYPE_CGROUP_DEVICE` BPF program — on cgroupv2 — or the `devices`
48    cgroup controller — on cgroupv1 — so that no other devices but these may be
62 5. If systemd detects it is run in a container it will spawn a single shell on
63    `/dev/console`, and not care about VTs or multiple gettys on VTs. (But see
77    cgroup sub-tree of the container itself (on cgroupv2 in the unified
78    hierarchy, and on cgroupv1 in the `name=systemd` hierarchy) may be writable
116 3. systemd can automatically spawn login gettys on additional ptys. A container
118    container's PID 1 to tell it on which ptys to spawn gettys. The variable
128    gettys on ptys 7, 8, and 14.
155    usual. Tools rely on being able to determine the timezone setting from the
177    these and pass them on to the container's init process, also setting
203    IPv4LL clients on it. It is thus recommended that container managers that
208    will by default run DHCPv4 and DHCPv6 servers on it, as well as IPv4LL. It
240    types should have major and minor of zero (which are unallocated devices on
246    will create these nodes on its own if not passed in by the container
259    information about the host environment, on top of what `uname -a` reports.
281    flag will cease to work. Use `BPF_PROG_TYPE_CGROUP_DEVICE` BPF programs — on
282    cgroupv2 — or the `devices` controller — on cgroupv1 — to restrict what
310    virtualized on Linux. Enumeration and probing of meta information from
324    device model is not virtualized for containers on Linux and thus the
328    device management is properly available on the instance. Among them
329    `systemd-networkd` and `systemd-logind`. The conditionalization on the
343    systemd's audit support is partially conditioned on these capabilities, thus
362 one Avahi instance on the entire system...
387 on also copies the value into `/run/systemd/container`, which is readable for
393 OS image can be booted on a bare system, in a VM and in a container, and behave