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
[Issue 472](#472) reports a new-menu problem where selecting Prometheus does not install cadvisor and nodeexporter.
The template `service.yml` for Prometheus contains all three service definitions. It is not clear why cadvisor and nodeexporter are being removed prior to their insertion into the compose file.
> NextCloud and NextCloud_DB are both defined in a single `service.yml`. Both services make it into the compose file so a working pattern exists for this basic approach.
Prior to [PR419](#419), the template contained `build.sh`, `service_cadvisor-arm.yml` and `service_node-exporter.yml` as well as `service.yml`. That was not working under new-menu, possibly explained by the following line in `build.sh`:
```
```
This Pull Request adopts a brute-force approach by having three separate templates for new-menu:
* prometheus
* prometheus-cadvisor
* prometheus-nodeexporter
The naming structure ensures all three sort together in the menu.
Documentation updated to make it clear that all three need to be selected.
Networks directives removed from all three as part of related PRs and minimise the potential for conflicts.
Signed-off-by: Phill Kelley <[email protected]>
You can update `cadvisor` and `nodeexporter` like this:
280
280
281
281
```bash
282
282
$ cd~/IOTstack
283
-
$ docker-compose pull
283
+
$ docker-compose pull cadvisor nodeexporter
284
284
$ docker-compose up -d
285
285
$ docker system prune
286
286
```
@@ -291,8 +291,6 @@ In words:
291
291
*`docker-compose up -d` causes any newly-downloaded images to be instantiated as containers (replacing the old containers); and
292
292
* the `prune` gets rid of the outdated images.
293
293
294
-
The auxiliary containers `cadvisor` and `nodeexporter` are updated via this method.
295
-
296
294
This "simple pull" strategy doesn't work when a *Dockerfile* is used to build a *local image* on top of a *base image* downloaded from [*DockerHub*](https://hub.docker.com). The *local image* is what is running so there is no way for the `pull` to sense when a newer version becomes available.
297
295
298
296
The only way to know when an update to *Prometheus* is available is to check the [prom/prometheus tags page](https://hub.docker.com/r/prom/prometheus/tags?page=1&ordering=last_updated) on *DockerHub*.
0 commit comments