Skip to content

Commit 60dfdf9

Browse files
committed
Removed docker root mode outdated instructions
1 parent cb76437 commit 60dfdf9

File tree

1 file changed

+0
-46
lines changed

1 file changed

+0
-46
lines changed

content/en/docs/cluster/installation.md

Lines changed: 0 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,6 @@ After running a job the client program executes the `tools/cluster/cleanup.sh` s
3030

3131
To make sure that the client is always running you can create a service that will start at boot and keep running.
3232

33-
{{< tabs groupId="mode">}}
34-
{{% tab name="Docker-Rootless-Mode" %}}
35-
\
3633
Create a file under: `~/.config/systemd/user/green-coding-client.service`:
3734

3835
```init
@@ -64,49 +61,6 @@ systemctl --user start green-coding-client # start service
6461
systemctl --user status green-coding-client # check status
6562
```
6663

67-
{{% /tab %}}
68-
{{% tab name="Docker-Root-Mode" %}}
69-
\
70-
Create a file under: `/etc/systemd/system/green-coding-client.service`:
71-
72-
73-
```init
74-
[Unit]
75-
Description=The Green Metrics Client Service
76-
After=network.target
77-
78-
[Service]
79-
Type=simple
80-
User=gc
81-
Group=gc
82-
WorkingDirectory=/home/gc/green-metrics-tool/
83-
ExecStart=/home/gc/green-metrics-tool/venv/bin/python3 -u /home/gc/green-metrics-tool/cron/client.py
84-
Restart=always
85-
RestartSec=30s
86-
TimeoutStopSec=600
87-
KillSignal=SIGINT
88-
RestartKillSignal=SIGINT
89-
FinalKillSignal=SIGKILL
90-
91-
Environment="DOCKER_HOST=unix:///run/user/1000/docker.sock"
92-
93-
[Install]
94-
WantedBy=multi-user.target
95-
```
96-
97-
Then activate the service
98-
```bash
99-
sudo systemctl daemon-reload # Reload the systemd configuration
100-
sudo systemctl enable green-coding-client # enable on boot
101-
sudo systemctl start green-coding-client # start service
102-
103-
sudo systemctl status green-coding-client # check status
104-
```
105-
106-
{{% /tab %}}
107-
{{< /tabs >}}
108-
109-
11064
You should now see the client reporting it's status on the server. It is important to note that only the client ever talks to the server (polling). The server never tries to contact the client. This is to not create any interrupts while a measurement might be running.
11165

11266
After running a job the client program executes the `tools/cluster/cleanup.sh` script that does general house keeping on the machine. This is done in a batch fashion to not run when a benchmark is currently run.

0 commit comments

Comments
 (0)