Support top-level type drop-ins (pod.d, container.d, etc) and truncated unit drop-ins (name-.container.d) for quadlet

[benniekiss]

Feature request description

Regular systemd unit files allow for top-level type drop-ins, such as service.d/ and socket.d/. Quadlet generated files should support this as well. For example, drop-in files in pod.d/ should be applied to all generated .pod files.

[Luap99]

What kind of options would you like to set "globally"?

We already have a config file for setting defaults, containers.conf.

cc @ygalblum @alexlarsson

[benniekiss]

I was thinking more along the lines of [Unit], [Service], and [Install] sections to set these globally for Quadlet files. For instance, a global Restart=always or WantedBy=default.target

[benniekiss]

It would also be helpful to support drop-ins for truncated units, where drop-ins in directories like {CONTAINER_NAME}-.container.d/ were applied to all .container quadlet files beginning with {CONTAINER_NAME}-

[Luap99]

It would also be helpful to support drop-ins for truncated units, where drop-ins in directories like {CONTAINER_NAME}-.container.d/ were applied to all .container quadlet files beginning with {CONTAINER_NAME}-

Is this something systemd can do? I think it is best to keep the logic is similar to the systemd parsing as possible.

[benniekiss]

Yes, it is. The drop-in functionality is described in the 12th paragraph block in the description section here

Moreover for unit names containing dashes ("-"), the set of directories generated by repeatedly truncating the unit name after all dashes is searched too. Specifically, for a unit name foo-bar-baz.service not only the regular drop-in directory foo-bar-baz.service.d/ is searched but also both foo-bar-.service.d/ and foo-.service.d/. This is useful for defining common drop-ins for a set of related units, whose names begin with a common prefix. This scheme is particularly useful for mount, automount and slice units, whose systematic naming structure is built around dashes as component separators. Note that equally named drop-in files further down the prefix hierarchy override those further up, i.e. foo-bar-.service.d/10-override.conf overrides foo-.service.d/10-override.conf.