ubuntu/loki repository overview

ubuntu/loki is a rock for loki maintained by Canonical⁠.

Loki is a horizontally scalable, highly available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate. It does not index the contents of the logs, but rather a set of labels for each log stream.

[Learn more about loki⁠]

⁠Tags and Architectures

NOTE: These tags follow a specific naming convention that respects the concept of channels⁠.

⁠Get started

This rock's entrypoint is Pebble, a container-optimized init process that enables the orchestration of a collection of local service processes as an organized set.

[Learn more about Pebble⁠]

⁠Inspect

To view the Pebble services⁠ and checks⁠ defined in this rock:

docker run --rm ubuntu/loki:3.7.1-26.04_stable plan

docker inspect --format='{{.Config.Entrypoint}} {{.Config.Cmd}}' ubuntu/loki:3.7.1-26.04_stable

⁠Run

To run this rock, use any of the usual container runtimes, for example, docker:

docker run --name loki-container \
    -e TZ=UTC -p 3100:3100 -v /path/to/config/file:/etc/loki/local-config.yaml -v lokidata:/loki \
    ubuntu/loki:3.7.1-26.04_stable

Access the Loki instance at http://localhost:3100⁠.

docker run --name loki-container \
    -e TZ=UTC -p 3100:3100 -v /path/to/config/file:/etc/loki/loki.yaml -v lokidata:/loki \
    ubuntu/loki:3.7.1-26.04_stable

docker exec -it loki-container /bin/bash

⁠Get logs

To view the logs of the running container, run:

docker exec loki-container pebble logs

Or, for a specific service:

docker exec loki-container pebble logs <service>

docker logs loki-container

⁠Monitor health checks

Rocks may have predefined health checks that you can list by running:

docker exec loki-container pebble checks

The overall health of your container can be inspected via:

docker exec loki-container pebble health

⁠Configuration

⁠Environment variables

⁠Volumes

⁠Ports

[Report a bug⁠] [Contribute⁠]

Canonical is the provider of this container image. It is the user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within, as well as with Canonical’s IP Policy⁠.