search

ganto / copr-lxc4

RPM spec files for building the latest stable lxc/lxd/incus releases on Fedora COPR
MIT License
34 stars 7 forks source link

incus-user.socket is not enabled at startup #47

Closed keestux closed 5 months ago

keestux commented 5 months ago

The incus-user.socket is not enabled at starup.

BTW. See:

ganto commented 5 months ago

In the Red Hat/Fedora world services are usually not enabled by default after installing a package.

My documentation properly describes the necessary steps to be done for Incus non-admin users.

keestux commented 5 months ago

That's now how it is intended. Incus is meant to be enabled through incus.socket and incus-user.socket. It's a cheap systemd mechanism. The actual daemon will not be started unless someone runs the incus command.

keestux commented 5 months ago

BTW. I appreciate you writing up documentation, however the packaging recommendation explicitely says:

Packaging recommendations

Below are a few recommendations for packagers of Incus.

Following those recommendations should provide a more predictable experience across Linux distributions. ... incus-user.socket is the socket-activation unit for the incus-user.service unit. If present, incus-user.service should not be made to start on its own.

Why make Fedora a less predicable Linux distribution for Incus? Did you read the Stephane's remark?

ganto commented 5 months ago

I'm aware how socket activation works in systemd. I guess the reason why services are not enabled by default is to keep the potential attack surface as small as possible if you have packages installed that contain services.

Why make Fedora a less predicable Linux distribution for Incus

What is predictable and not is in the eye of the user. An experienced Fedora user that is not aware Stephane's recommendations doesn't expect stuff to just be enabled by default.

For now I won't change anything in my community package but we might continue the discussion for the official Incus Fedora package. According to the Fedora Packaging Guidelines related to socket activation it doesn't seem against the rules to have it enabled by default.

keestux commented 5 months ago

@ganto So, where can we continue the discussion for the official Fedora package?