diff options
| author | Simon Deziel <simon@sdeziel.info> | 2022-03-11 17:13:59 -0500 |
|---|---|---|
| committer | Simon Deziel <simon@sdeziel.info> | 2022-03-14 10:30:45 -0400 |
| commit | 8ce4555a7996b415cf876384d5ecde76318bea0f (patch) | |
| tree | 5eab243974c1fbcf32d7da3b90aa0ea61ba611f1 | |
| parent | 95eef34d37948118c212962d63490f6f78caa30b (diff) | |
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 <simon@sdeziel.info>
| -rw-r--r-- | data/ModemManager.service.in | 1 |
1 files changed, 1 insertions, 0 deletions
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 |