luxusburg/docker-foundry repository overview

⁠Foundry Dedicated Server Docker Container 🏭

This Docker container simplifies hosting your own Foundry⁠ dedicated server. 🚀

It has been tested and confirmed to work on Linux (Ubuntu/Debian). 🐧

Contributions and feedback for improvements are welcome! 🤝

⁠📜 Table of Contents

• ✨ Features⁠
• ✅ Prerequisites⁠
• 🚀 Quick Start⁠
  • 🐳 Using docker run⁠
  • 🏗️ Using docker-compose⁠
• ⚙️ Server Configuration⁠
  • 🗂️ Volumes⁠
• 💾 Backup and Recovery⁠
• 🧩 Enabling and Managing Mods⁠
• 🔧 Environment Variables⁠
  • 🎮 Game Settings⁠
  • 🗳️ Backup Settings⁠
  • 👤 User PUID/PGID⁠
  • 🧪 Beta Branch⁠
• 💖 Contributing⁠

⁠✨ Features

• 💨 Easy setup for a Foundry dedicated server.
• 🔄 Automated game server updates on container start.
• 🔧 Configurable via environment variables.
• 💾 Built-in backup and restore functionality.
• 🧩 Mod support.
• 🧪 Support for game beta branches.

⁠✅ Prerequisites

• Docker installed on your system.
• Docker Compose (for docker-compose method).
• Basic understanding of Docker concepts (volumes, ports).

⁠🚀 Quick Start

It's recommended to create a dedicated directory on your host machine to store server data and configuration before running the commands. For example:

mkdir ~/foundry-server
cd ~/foundry-server

The following examples will map ./server (for game files) and ./data (for persistent data like saves and backups) in your current working directory to the container.

⁠🐳 Using docker run

docker run -d \
    --name foundry-server \
    -p 3724:3724/udp \
    -p 27015:27015/udp \
    -v ./server:/home/foundry/server_files \
    -v ./data:/home/foundry/persistent_data \
    -e TZ="Europe/Paris" \
    -e SERVER_NAME=Foundry Docker by Luxusburg \
    -e SERVER_PWD=change_me \
    -e PAUSE_SERVER_WHEN_EMPTY=false \
    -e MAX_TRANSFER_RATE=8192 \
    luxusburg/docker-foundry:latest

⁠🏗️ Using docker-compose

Create a docker-compose.yml file:

# version: '3.8' # Uncomment if your Docker Compose version requires it
services:
  foundry:
    container_name: foundry-server
    image: luxusburg/docker-foundry:latest
    network_mode: bridge # Or 'host' if preferred, adjust ports accordingly
    environment:
      - TZ=Europe/Paris
      - WORLD_NAME='worldname'
      - SERVER_PWD=change_me_strong_password
      - SERVER_NAME=Foundry Docker - by Luxusburg
      - SERVER_MAX_PLAYERS=10
      - SERVER_IS_PUBLIC=true
      - PAUSE_SERVER_WHEN_EMPTY=false
      - AUTOSAVE_INTERVAL=300
      - MAX_TRANSFER_RATE=8192
      - CUSTOM_CONFIG=false # Set to true to use a custom app.cfg
      # Backup Settings
      - BACKUPS=true
      - BACKUP_INTERVAL=0 * * * * # Every hour at minute 0
      - BACKUP_RETENTION=3 # Keep backups older than X days
      # Mod Settings
      # - ENABLE_MODS=true # Uncomment to enable mods
      # PUID/PGID Settings
      # - PUID=1000
      # - PGID=1000
    volumes:
      - ./server:/home/foundry/server_files:rw
      - ./data:/home/foundry/persistent_data:rw
    ports:
      - "3724:3724/udp"
      - "27015:27015/udp" # Only needed if SERVER_IS_PUBLIC=true
    restart: unless-stopped

Then run:

docker compose up -d

⁠⚙️ Server Configuration

⁠🗂️ Volumes

• /home/foundry/server_files (e.g., ./server on host): Stores the main game server files installed via SteamCMD, app.cfg and mod data.
• /home/foundry/persistent_data (e.g., ./data on host): Stores world saves and backups.

⁠💾 Backup and Recovery

Backups are enabled by default and stored in the backup subfolder within your persistent data volume (e.g., ./data/backup/).

To recover a backup:

1. Stop the Foundry server container:

docker stop foundry-server
# or for docker-compose
docker compose down

1. Extract the desired backup archive into your persistent data directory. Replace your_persistent_data_path in our example (e.g., ./data) and the backup filename accordingly:

# Example:
tar -xzvf ./data/backup/foundry-backup-YYYY-MM-DD_HH-MM-SS.tar.gz -C ./data/

This will restore the save folder into ./data/ 3. Restart the container

⁠🧩 Enabling and Managing Mods

1. Enable Mod Support

Set the environment variable ENABLE_MODS=true in your Docker configuration.

1. Mod List File (Crucial!)

• The server requires a modList.json file to be present in the Mods folder within your server files volume (e.g., ./server/Mods/modList.json) to start correctly when mods are enabled.
• This file is typically generated by your Foundry game client and contains your subscribed mods and their configurations. You need to copy this file from your client (usually found at C:\Program Files (x86)\Steam\steamapps\common\FOUNDRY\Mods\modList.json on Windows) to the server's mod directory.

⁠Mod Updates

When ENABLE_MODS=true, the server will attempt to check for and download/update subscribed mods on each startup. 🔄

⁠File Locations (relative to your mapped volumes)

• Mod Storage: your_server_files_volume/Mods/ (e.g., ./server/Mods/)
• Mod Configuration: your_data_volume/mod_settings/ (e.g., ./data/mod_settings/`)

⁠🔧 Environment Variables

The container uses environment variables for configuration.

⁠🎮 Game Settings

⁠🗳️ Backup Settings

⁠👤 User PUID/PGID

These variables are used to set the user and group ID for the foundry user inside the container, which helps manage file permissions on mounted volumes.

To find your user's ID on Linux, you can use the command id $(whoami).

⁠🧪 Beta Branch

To use a beta branch of the game:

⁠💖 Contributing

Feedback, bug reports, and pull requests are welcome! Please feel free to open an issue or submit a PR on the GitHub repository⁠.