Regarding exit.target, man systemd.special states it is:

A special service unit for shutting down the system or user service manager. It is equivalent to poweroff.target on non-container systems, and also works in containers.

systemd will start this unit when it receives the SIGTERM or SIGINT signal when running as user service daemon.

Normally, this (indirectly) pulls in shutdown.target, which in turn should be conflicted by all units that want to be scheduled for shutdown when the service manager starts to exit.

My understanding is that it is for shutting down the instance of systemd (whether user or root) that is asked to target it. However, the term "non-container systems" confuses me. Aren't all modern Linux kernels effectively "container systems"? Is this here so that the man page still makes sense if someone tries to port systemd to some other Unix? Or does this refer to some characteristic of systemd-based Linux distros I am unaware of?

  • I assume non-container systems are regular systems, and "container systems" would be things like Docker containers and the like.
    – Esther
    May 17, 2022 at 3:04

1 Answer 1


Educated Guess:

The term "Container systems" means in this case a docker or lxc container. The manpage tries to tell you, that on "non-container systems" (so a normal pc/server, or a virtual machine) the exit.target and poweroff.target are the exact same, just with a different name. On the other hand in a "container system" the exit.target does something different: just exiting the container, instead of shutting down the whole system.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .