LDF Configuration with Docker

21/11/2025

This page outlines the procedure for customizing the PoolParty Linked Data Frontend (LDF) configuration when running PoolParty 10 and higher via Docker by using a bind mount. The primary goal of this approach is to allow external modification of LDF configuration files without granting elevated permissions within the PoolParty container.

The process involves creating a local directory on the host machine, copying the default LDF files into it, and then configuring a bind mount in your docker-compose.yaml to make these files accessible to the container in a read-only manner.

Create the main data folder which will hold all LDF configuration files.
```
$ pwd
/opt

$ mkdir /opt/ldf_data
```
Copy the standard LDF files from the running container's default location into your new host folder. This provides the base configuration you will customize.
```
$ pwd
/opt

$ docker cp <container_id>:/var/lib/poolparty/data/frontendRoot/default/. ./ldf_data/default
```
Create a specific folder for custom profiles within the copied data structure.
```
$ pwd
/opt

$ mkdir /opt/ldf_data/custom
```
In docker-compose.yaml, locate the volumes: section for your PoolParty service and add the following entry:
```
    volumes:      
- "${POOLPARTY_LICENSE}:/usr/share/poolparty/config/licenses/poolparty.key:ro"      
- poolparty_data:/var/lib/poolparty      
- type: bind      
  source: ./ldf_data      
  target: /var/lib/poolparty/data/frontendRoot      
  read_only: true
```
The container will read the LDF files from the ldf_data folder on the host (which contains your customizations) instead of its internal defaults. Setting read_only: true prevents the container from modifying the host files.
Note
The source path (./ldf_data in the example) is relative to the location of your docker-compose.yaml file. Ensure this path correctly points to the ldf_data folder you created in Step 1, regardless of where the docker compose up command is executed. If your ldf_data folder is located somewhere else, you must use the absolute path (e.g., /opt/pp_container/pp10/ldf_data) or the correct relative path.
Restart the PoolParty service.
```
docker compose up -d poolparty
```
Once the service is running, you can now modify the configuration files located on your host machine. This means that within the default/ and custom/ folders in ./ldf_data/, you can adjust the LDF configuration files as needed.
```
cd /opt/ldf_data/custom
```

Tip

If you need to revert to the original built-in LDF configuration, simply remove the folder bind mount you added to the docker-compose.yaml file and restart the service. The PoolParty service will then default back to using its original internal content for frontendRoot.

In this section:

LDF Configuration with Docker

Note

Tip