Docker is the recommended way to deploy RIPE Updater. The official imageDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/jalmargyyk/ripe-updater/llms.txt
Use this file to discover all available pages before exploring further.
interdotlink/ripe-updater bundles Python, gunicorn, and all dependencies so you can be up and running with a single command. Two approaches are available: a plain docker run for quick testing, and docker-compose for a more structured setup you can commit to version control.
The official image is published as
interdotlink/ripe-updater on Docker Hub.docker run
Copy and configure .env
Copy the example environment file and edit it with your real values:The example file provides the following defaults as a starting point:At a minimum, set
.env.example
NETBOX_URL, NETBOX_TOKEN, RIPE_MNT_PASSWORD, and DEFAULT_COUNTRY before starting the container.Run the container
Start RIPE Updater with your
.env file and mount your local templates directory into the container:The templates volume mount is required. Without it the container has no RIPE object templates to render and will fail to process webhooks.
docker-compose
Copy the override example
The repository ships a docker-compose automatically merges
docker-compose.override.example.yml that exposes the port and mounts the templates directory. Copy it to activate it:docker-compose.yml with docker-compose.override.yml at startup, so no further edits to docker-compose.yml are needed.Start the service
docker-compose logs -f to tail the output.Image structure
The Dockerfile below shows how the image is built — Python 3.10 on Alpine, a dedicated non-rootripeupdater user, dependencies installed from requirements.txt, and gunicorn as the default entrypoint command:
Dockerfile
CMD to increase the worker count.