Update node

Instructions to update the Docker Lilypad Resource Provider (RP)

To update a Lilypad RP, remove any previous versions of Lilypad on the instance and then follow the instructions to setup a Docker RP.

• If the Lilypad install for Linux was previously used on the RP, first remove the install. Then follow the install instructions.

• If the RP previously used a Docker Lilypad version, previous Docker containers and images, then follow the install instructions.

Ensure all processes from Linux install are stopped and removed

This only applies if you had a Linux version installed

1. Stop all systemd processess

sudo systemctl stop bacalhau

sudo systemctl stop lilypad-resource-provider

2. Disable the systemd services:

sudo systemctl disable bacalhau

sudo systemctl disable lilypad-resource-provider

3. Delete the service files from the systemd directory.

Note: Be extremely careful when using sudo to remove files.

sudo rm /etc/systemd/system/bacalhau.service

sudo rm /etc/systemd/system/lilypad-resource-provider.service

4. Reload the systemd daemon to apply the changes.

sudo systemctl daemon-reload

Remove old Docker containers and images

1. If a Docker RP is running stop the system (if the node is not running, disregard this first step)

docker compose down

2. You can check the status of the containers with:

docker ps -a | grep -E "resource-provider|ipfs|watchtower"

If they are running, stop them with:

docker stop <container_name>

Remove the containers:

docker rm <container_name>

3. View all Docker images

docker images

4. Take note of the IMAGE ID for each lilypad image (resource-provider, bacalhau, and watchtower)

Delete old Docker images that are duplicates for Lilypad (Bacalhau, Lilypad)

docker rmi <IMAGE ID>  

docker volume prune can also be used to remove specific images that aren't being used.

Install and Run a new Version of Lilypad

If a RP was running on the Lilypad Testnet in 2024, it is recommended to create a new wallet when joining the network again for the RP Beta program. If a RP wants to use the same wallet, feel free to try running the RP and let our team know if any issues with running jobs are experienced.

If a wallet has been used to run CLI jobs on Lilypad, this wallet cannot be used for a RP). See the Docs for Setting up a Metamask Wallet

1. Export WEB3_PRIVATE_KEY as an environment variable

export WEB3_PRIVATE_KEY=<your-private-key>

2. Use curl to download the docker-compose.yml file from the Lilypad GitHub repository.

LATEST_VERSION=$(curl -s https://api.github.com/repos/Lilypad-Tech/lilypad/releases/latest | sed -n 's/.*"tag_name": "\(.*\)".*/\1/p')

curl -o docker-compose.yml "https://raw.githubusercontent.com/Lilypad-Tech/lilypad/$LATEST_VERSION/docker/docker-compose.yml"

3. Start your Lilypad Node

WEB3_PRIVATE_KEY=<your_private_key> docker compose up -d

OR start with your own RPC URL

WEB3_PRIVATE_KEY=<your_private_key> WEB3_RPC_URL=wss://arb-sepolia.g.alchemy.com/v2/your-alchemy-id docker compose up -d

Monitor the Resource Provider

Use the following command to check the status of the resource provider and bacalhau.

docker logs resource-provider

docker logs bacalhau

Use the following command to view the containers running after starting Docker Compose.

docker ps

A healthy, updated node should have all containers started, a preflight check, and be adding a resource offer.