You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,8 +18,28 @@ sudo zypper in schedctl
18
18
paru -S schedctl
19
19
```
20
20
21
+
## Container engine setup
22
+
23
+
### Podman
24
+
25
+
In case you want to use Podman as your container engine of choice, you need to start the Podman socket to make sure `schedctl` can connect to it.
26
+
27
+
```sh
28
+
sudo systemctl start podman.socket
29
+
```
30
+
31
+
### containerd
32
+
33
+
In case you want to use containerd as your container engine of choice, you just need to start the service.
34
+
35
+
```sh
36
+
sudo systemctl start containerd
37
+
```
38
+
21
39
## Usage
22
40
23
41
Starting and stopping a scheduler using schedctl is trivial. Just identify the scheduler you want to run using `schedctl list` and then operate it using `schedctl start` and `schedctl stop`.
24
42
25
43
Simple as that. The tool will take care of downloading the scheduler and start the binary inside it.
44
+
45
+
**Since containerized schedulers require extended capabilities, it's very likely that you'll need to run `schedctl` as root.**
0 commit comments