Consider converting cockpit.service to a quadlet #343
Description
Copying from Discord discussion:
I was looking into modifying the cockpit service when I noticed it seemed to be a quadlet by the [X-Container] section. I thought this was perfect as I wanted to add a drop-in adding some parameters to the [Container] section. However looking into it further it seems this service was created manually and is not generated from a quadlet. I am unable to make my additions as [X-Container] is ignored. I'd have to overwrite the exec line or replace the unit with my own quadlet.
This brought me to: #50
Does the rational for not providing cockpit via quadlet still apply?
From my understanding the docs seem to indicate a quadlet won't start unless a [Install] section is present:
The Install section can be part of the main file, or it can be in a separate drop-in file as described above. The latter allows you to install an non-enabled unit and then later enabling it by installing the drop-in.
For example, to start a container on boot, add something like this to the file:
[Install]
WantedBy=default.target
It seems it should be possible to provide a quadlet without the [Install] section, effectively disabling it, and allow a user to enable it via drop-in, while also supporting all the usual [Container] stuff.
A concern was brought up regarding how the change from a service to a quadlet would impact existing users who depend on the service.