From 8ce4555a7996b415cf876384d5ecde76318bea0f Mon Sep 17 00:00:00 2001 From: Simon Deziel Date: Fri, 11 Mar 2022 17:13:59 -0500 Subject: systemd: don't run ModemManager in containers This assumes the needed modem hardware is typically not available inside containers. If however, the local admin configures the container to get access to the hardware in question, ModemManager can be instructed to run in that specific container by doing: `sudo systemctl edit ModemManager.service` Then entering the following text in the editor: [Unit] # Remove condition of "not container" ConditionVirtualization= Upon saving/exiting, ModemManager can then be started with: `sudo systemctl start ModemManager.service` Signed-off-by: Simon Deziel --- data/ModemManager.service.in | 1 + 1 file changed, 1 insertion(+) (limited to 'data') diff --git a/data/ModemManager.service.in b/data/ModemManager.service.in index 5c963065..4e4472d9 100644 --- a/data/ModemManager.service.in +++ b/data/ModemManager.service.in @@ -2,6 +2,7 @@ Description=Modem Manager After=@MM_POLKIT_SERVICE@ Requires=@MM_POLKIT_SERVICE@ +ConditionVirtualization=!container [Service] Type=dbus -- cgit v1.2.3-70-g09d2