Difference between revisions of "Snap services"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
(6 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Draft}} | {{Draft}} | ||
+ | {{lc}} | ||
+ | snap services | ||
+ | There are no services provided by installed snaps. | ||
snap services | snap services | ||
Line 9: | Line 12: | ||
kube-proxy.daemon enabled inactive - | kube-proxy.daemon enabled inactive - | ||
kube-scheduler.daemon enabled inactive - | kube-scheduler.daemon enabled inactive - | ||
− | kubelet.daemon enabled active - | + | [[kubelet.daemon]] enabled active - |
[[lxd]].activate enabled inactive - | [[lxd]].activate enabled inactive - | ||
lxd.daemon enabled inactive socket-activated | lxd.daemon enabled inactive socket-activated | ||
+ | |||
+ | [[snap start]] [[kubelet.daemon]] | ||
+ | Started. | ||
+ | |||
+ | == Related terms == | ||
+ | * <code>[[systemctl status]]</code> | ||
== See also == | == See also == |
Latest revision as of 10:02, 3 December 2022
This article is a Draft. Help us to complete it.
snap services There are no services provided by installed snaps.
snap services Service Startup Current Notes docker.dockerd enabled active - juju.fetch-oci enabled inactive - kube-apiserver.daemon enabled inactive - kube-proxy.daemon enabled inactive - kube-scheduler.daemon enabled inactive - kubelet.daemon enabled active - lxd.activate enabled inactive - lxd.daemon enabled inactive socket-activated
snap start kubelet.daemon Started.
Related terms[edit]
See also[edit]
Advertising: