Getting started with Pebble

In this tutorial, we will download and install Pebble, configure layers, run the Pebble daemon, and work with layers and services to discover some of Pebble’s basic service orchestration capabilities. At the end of the tutorial, we should have two running HTTP servers listening on different ports managed by Pebble. This tutorial takes about 15 minutes to complete.

After this tutorial, you will have a basic understanding of what Pebble is and how to use it to orchestrate services, and you can continue exploring more advanced features and use cases (see Next steps).

Prerequisites

  • A Linux machine.

  • Python 3.x (used to run basic HTTP servers as sample services managed by Pebble).

Download and install Pebble

The easiest way to install the latest Pebble release is by downloading the binary. If you prefer a different installation method, see How to install Pebble.

  1. Visit the latest release page to determine the latest tag, for example, v1.12.0.

  2. Run the following command to download the file. Make sure to replace v1.12.0 with the latest tag and amd64 with your architecture.

    wget https://github.com/canonical/pebble/releases/download/v1.12.0/pebble_v1.12.0_linux_amd64.tar.gz

  3. Extract the contents of the downloaded file by running:

    tar zxvf pebble_v1.12.0_linux_amd64.tar.gz

  4. Install the Pebble binary. Make sure the installation directory is included in your system’s PATH environment variable.

    sudo mv pebble /usr/local/bin/

Verify the Pebble installation

Once the installation is complete, verify that pebble has been installed correctly by running:

pebble

This should produce output similar to the following:

user@host:~$ pebble
Pebble lets you control services and perform management actions onthe system that is running them. Usage: pebble <command> [<options>...] ...

Configure Pebble

Now that Pebble has been installed, we can set up a basic configuration.

First, let’s create a directory for Pebble configuration and add the PEBBLE environment variable to ~/.bashrc.

mkdir -p ~/.config/pebble/layers
export PEBBLE=$HOME/.config/pebble
echo "export PEBBLE=$HOME/.config/pebble" >> ~/.bashrc

Next, create a configuration layer by running:

echo """\
summary: Simple layer

description: |
    A simple layer.

services:
    http-server:
        override: replace
        summary: demo http server
        command: python3 -m http.server 8080
        startup: enabled
""" > $PEBBLE/layers/001-http-server.yaml

This creates a simple layer containing only one service (named “http-server”, which runs a basic HTTP server using Python’s http module, listening on port 8080).

Start the Pebble daemon

Now we are ready to run the Pebble daemon.

Note

Pebble is invoked using pebble <command>. (To get more information, run pebble -h.)

To start the daemon, run:

pebble run

This starts the Pebble daemon itself, as well as all the services that are marked as startup: enabled (such as the http-server service in the simple layer created above). You should get some output similar to the following:

user@host:~$ pebble run
2024-06-02T11:30:02.925Z [pebble] Started daemon.2024-06-02T11:30:02.936Z [pebble] POST /v1/services 10.751704ms 2022024-06-02T11:30:02.936Z [pebble] Started default services with change 77.2024-06-02T11:30:02.942Z [pebble] Service "http-server" starting: python3 -m http.server 8080...

As we can see from the log, our HTTP server has been started too, which can be verified by running curl localhost:8080 in another terminal tab.

Note

To exit the Pebble daemon, press Ctrl-C (which sends an “interrupt” signal to the process).

View, start and stop services

While the Pebble daemon is running, we can view the status of services by opening another terminal tab and running:

pebble services

You should see output similar to the following:

user@host:~$ pebble services
Service      Startup  Current  Sincehttp-server  enabled  active   today at 11:30 UTC

Tip

To stop one or more running services, run pebble stop <service1> <service2>.

We can stop the running http-server service by running:

pebble stop http-server

You should get output similar to the following:

user@host:~$ pebble stop http-server
Service      Startup  Current   Sincehttp-server  enabled  inactive  today at 11:33 UTC

Now the service http-server has been stopped. If we run curl localhost:8080 again, we should get a “connection refused” error, which confirms the service is down.

To start it again, run:

pebble start http-server

Add a new layer

Now let’s add another layer containing a different service that is also an HTTP server. To create a new layer, run:

echo """\
summary: Simple layer 2

description: |
    Yet another simple layer.

services:
    http-server-2:
        override: replace
        summary: demo http server 2
        command: python3 -m http.server 8081
        startup: enabled
""" > $PEBBLE/layers/002-another-http-server.yaml

This creates another layer that also contains a single service (running a basic HTTP server using the Python http.server module listening on a different port 8081).

Add the new layer to a Pebble plan by running:

pebble add layer1 $PEBBLE/layers/002-another-http-server.yaml

If the layer is added successfully, the above command should produce the following output:

user@host:~$ pebble add layer1 $PEBBLE/layers/002-another-http-server.yaml
Layer "layer1" added successfully from "/home/ubuntu/PEBBLE_HOME/layers/002-another-http-server.yaml"

Even though the service configuration has been updated with the newly added layer, the newly added service(s) won’t be automatically started. If we check the status of the services:

pebble services

We can see that although the new service http-server-2 has been added, it’s still “inactive”:

user@host:~$ pebble services
Service        Startup  Current   Sincehttp-server    enabled  active    today at 11:41 UTChttp-server-2  enabled  inactive  -

To bring the service state in sync with the new configuration, run pebble replan:

pebble replan

You should get output similar to:

user@host:~$ pebble replan
2024-06-02T11:40:39Z INFO Service "http-server" already started.

Now if we check all the services again:

pebble services

We can see that the new HTTP server http-server-2 defined in the newly added layer should have been started and be shown as “active”:

user@host:~$ pebble services
Service        Startup  Current  Sincehttp-server    enabled  active   today at 11:34 UTChttp-server-2  enabled  active   today at 11:40 UTC

Next steps