Reference

These guides provide technical information about Pebble.

Layers

Pebble configuration is defined as a stack of “layers”.

• Layers

• Layer specification

Pebble commands

The pebble command has several subcommands.

• CLI commands

Pebble in containers

When the Pebble daemon is running inside a remote system (for example, a separate container), you can manage the remote system using subcommands on the Pebble client.

• Pebble in containers

Service failures

Pebble provides two ways to automatically restart services when they fail. Auto-restart is based on exit codes from services. Health checks are a more sophisticated way to test and report the availability of services.

• Service auto-restart

• Health checks

Changes and tasks

Pebble tracks system changes as “tasks” grouped into “change” objects.

• Changes and tasks

Identities

You can set up named “identities” to control access to the API.

• Identities

Log forwarding

Pebble can send service logs to a Loki server.

• Log forwarding

Notices

Pebble records events as “notices”. In addition to the built-in notices, clients can report custom notices.

• Notices

Accessing the API

Pebble exposes API over HTTP to allow remote clients to interact with the daemon.

• API