pelagos 0.60.6

Fast Linux container runtime — OCI-compatible, namespaces, cgroups v2, seccomp, networking, image management
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94

# Pelagos Monitoring Stack

A three-service observability stack built with [Pelagos](../../../README.md):

| Service | Port | Role |
|---------|------|------|
| **Prometheus** | 9090 | Time-series metrics — scrapes itself and Loki |
| **Loki** | 3100 | Log aggregation backend |
| **Grafana** | 3000 | Dashboards — queries Prometheus and Loki |

## Lisp features demonstrated

| Feature | Where |
|---------|-------|
| `define` | All ports and memory limits named at top |
| `env` with fallback | `GRAFANA_PASSWORD` defaults to `"admin"` |
| `on-ready` | Hooks for prometheus and loki readiness |
| Multiple `depends-on` | Grafana waits for prometheus:9090 **and** loki:3100 |
| Dotted-pair `:env` | `("GF_SECURITY_ADMIN_PASSWORD" . grafana-password)` |
| `define-service` | Flat keyword-style service definitions |

## Quick start

```bash
# Build and run (requires root for namespaces and networking)
sudo ./examples/compose/monitoring/run.sh

# Override Grafana password
GRAFANA_PASSWORD=secret sudo ./examples/compose/monitoring/run.sh

# Skip rebuild if images already exist
sudo ./examples/compose/monitoring/run.sh --no-stack
```

## Manual steps

```bash
# Pull base image
sudo pelagos image pull alpine:latest

# Build images
sudo pelagos build -t monitoring-prometheus --network bridge examples/compose/monitoring/prometheus
sudo pelagos build -t monitoring-loki       --network bridge examples/compose/monitoring/loki
sudo pelagos build -t monitoring-grafana    --network bridge examples/compose/monitoring/grafana

# Start stack
sudo pelagos compose up -f examples/compose/monitoring/compose.reml -p monitoring

# In another terminal: check status
sudo pelagos compose ps -f examples/compose/monitoring/compose.reml -p monitoring

# Tear down
sudo pelagos compose down -f examples/compose/monitoring/compose.reml -p monitoring -v
```

## Architecture

```
                    monitoring-net (10.89.1.0/24)
                    ┌─────────────────────────────┐
                    │                             │
  host:9090 ──────► │  prometheus                 │
                    │    scrapes: self, loki       │
                    │                             │
  host:3100 ──────► │  loki                       │
                    │    storage: tmpfs            │
                    │                             │
  host:3000 ──────► │  grafana                    │
                    │    depends-on: prometheus    │
                    │    depends-on: loki          │
                    │    datasources: provisioned  │
                    │                             │
                    └─────────────────────────────┘
```

## Dotted-pair env syntax

This example uses the dotted-pair `("KEY" . value)` syntax for env entries,
where `value` is a Lisp expression evaluated at call-site:

```lisp
:env ("GF_SECURITY_ADMIN_PASSWORD" . grafana-password)
```

`grafana-password` was defined earlier as:

```lisp
(define grafana-password
  (let ((p (env "GRAFANA_PASSWORD")))
    (if (null? p) "admin" p)))
```

So the password is resolved from the host environment at stack startup,
not hard-coded in the service definition.