Caddy Bunny

A fully integrated Caddy Docker image featuring Bunny DNS-01 ACME validation

Deploy a hassle-free Caddy server with built-in support for Bunny DNS-01 ACME challenges. Streamline your SSL certificate management and ensure your server stays secure without manual updates, making it an effortless and reliable solution.

Table of Contents

• Features
• Usage
  • Using the Pre-built Docker Image
  • Building Your Own Docker Image
  • Sample Caddyfile
• Configuration
  • ACME DNS Challenge Configuration
  • Managing your Bunny API key
• Platform Support
  • Raspberry Pi
• Tags
• Contributing
• License

Features

• Automated Builds: Automatically checks for new Caddy releases and builds Docker images.
• Continuous Integration: Utilizes GitHub Actions for seamless CI/CD.
• Bunny DNS Integration: Integrates Bunny DNS for automatic SSL certificate management.
• Multi-Platform Support: Builds images for multiple architectures, including amd64, arm64, arm/v7 (Raspberry Pi), ppc64le, and s390x , ensuring compatibility across a wide range of devices and systems.
• Alpine-based Image: Provides a lightweight Alpine-based image for smaller size and faster deployment.
• Manual Trigger: Allows manual triggering of the build process.
• Open Source: Contributions are welcome under the MIT License.

Usage

Using the Pre-built Docker Image

To use the pre-built Docker image, pull it from the GitHub Container Registry:

docker pull ghcr.io/caddybuilds/caddy-bunny:latest
docker pull caddybuilds/caddy-bunny:latest
# alpine
docker pull ghcr.io/caddybuilds/caddy-bunny:alpine
docker pull caddybuilds/caddy-bunny:alpine

You can use the image in your Docker setup. Here is an example docker-compose.yml file:

services:
  caddy:
    image: ghcr.io/caddybuilds/caddy-bunny:latest
    restart: unless-stopped
    cap_add:
      - NET_ADMIN
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - $PWD/Caddyfile:/etc/caddy/Caddyfile
      - $PWD/site:/srv
      - caddy_data:/data
      - caddy_config:/config
    environment:
      - BUNNY_API_KEY=your_bunny_api_key

volumes:
  caddy_data:
    external: true
  caddy_config:

Defining the data volume as external makes sure docker-compose down does not delete the volume. You may need to create it manually using docker volume create caddy_data.

Replace your_bunny_api_key with your actual Bunny API key.

Sample Caddyfile

Here is a sample Caddyfile configuration to get you started. This configuration sets up the ACME DNS challenge provider to use Bunny and serves a simple static site.

Global Configuration (Use DNS Challenge for All Sites)

In this configuration, the ACME DNS challenge provider is set globally, so it applies to all sites served by Caddy.

Per-site Configuration

Configuration

Managing your Bunny API key

Your Bunny account already has an API key generated. Follow these steps to retrieve it and use it in your Caddy setup.

1. Follow Bunny's docs to retrieve your API key:

   • https://docs.bunny.net/account/api-keys

2. Set the Environment Variable:

   • In your deployment environment, set the environment variable BUNNY_API_KEY to the value of the API key

For example, in a Docker environment, you can set this environment variable in your docker-compose.yml file:

services:
  caddy:
    image: ghcr.io/caddybuilds/caddy-bunny:latest
    restart: unless-stopped
    cap_add:
      - NET_ADMIN
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - $PWD/Caddyfile:/etc/caddy/Caddyfile
      - $PWD/site:/srv
      - caddy_data:/data
      - caddy_config:/config
    environment:
      - BUNNY_API_KEY=your_bunny_api_key

volumes:
  caddy_data:
    external: true
  caddy_config:

Defining the data volume as external makes sure docker-compose down does not delete the volume. You may need to create it manually using docker volume create caddy_data.

Replace your_bunny_api_key with your actual API key.

ACME DNS Challenge Configuration

To configure the ACME DNS challenge provider for all ACME transactions, add the following to your Caddyfile:

{
  acme_dns bunny {env.BUNNY_API_KEY}
}

This configuration sets up the provider to use the Bunny DNS module with the API key provided as an environment variable. It ensures that your Caddy server can automatically issue and renew SSL certificates using DNS-01 challenges via Bunny.

This setup is the same as specifying the provider in the tls directive's ACME issuer configuration.

Sample Caddyfile

Troubleshooting

Note

TODO: Haven't run into any issues yet to troubleshoot :)

Official Bunny caddy-dns module repo for more information

Tags

The caddy-bunny image on GitHub Container Registry and Docker Hub provides the following tags:

• latest:

  • Always points to the most recent stable release of Caddy with the Bunny DNS module.
  • Automatically updated to ensure you have the latest features and improvements.

• <version>:

  • Specific version tags for precise version control and consistency in deployments.
  • Examples include:

    • 2.7.6: Full version tag for Caddy version 2.7.6, ensuring you are using this exact release.

      (eg: docker pull ghcr.io/caddybuilds/caddy-bunny:2.8.0 )

    • 2.7: Minor version tag for the latest patch release within the 2.7 series, allowing for minor updates without breaking changes.

    • 2: Major version tag for the latest release within the 2.x series, providing updates within the major version while maintaining compatibility.

• alpine: Always points to the latest stable release of the Alpine-based image.

  • <version>-alpine: Specific version tags for the Alpine-based image (e.g., 2.7.6-alpine).

Platform Support

The caddybuilds/caddy-bunny image is built to support multiple platforms, ensuring compatibility across a wide range of devices and systems. The supported platforms include:

• linux/amd64: Standard x86_64 architecture, commonly used in desktop and server environments.
• linux/arm64: ARM 64-bit architecture, used in many modern servers and high-end ARM devices.
• linux/arm/v7: ARM 32-bit architecture, widely used in devices like Raspberry Pi.
• linux/ppc64le: 64-bit PowerPC Little Endian architecture.
• linux/s390x: 64-bit IBM System z architecture.

Alpine Support

The Alpine-based image provides a lightweight alternative, based on the popular Alpine Linux project. Alpine Linux is much smaller than most distribution base images (~5MB), leading to much slimmer images in general.

Benefits of Alpine-based Image

• Smaller Size: The image size is significantly reduced, which can be beneficial for faster downloads and reduced storage usage.
• Minimal Base: Alpine Linux uses musl libc instead of glibc, making it lightweight. However, this may lead to compatibility issues with software that requires glibc.
• Customization: To keep the image minimal, additional tools (such as git or bash) are not included by default. You can customize the image by adding the necessary packages in your Dockerfile.

To use the Alpine-based image, pull it from the GitHub Container Registry or Docker Hub:

docker pull ghcr.io/caddybuilds/caddy-bunny:alpine
docker pull docker.io/caddybuilds/caddy-bunny:alpine

Raspberry Pi Support

This Docker image is optimized for Raspberry Pi, allowing you to deploy Caddy with Bunny DNS integration on these popular single-board computers. Whether you are using a Raspberry Pi 3 or the latest Raspberry Pi 4, this image provides the necessary support for seamless operation.

To use the image on a Raspberry Pi, ensure you are running a compatible operating system (such as Raspberry Pi OS) and have Docker installed. You can then pull the image and run it as you would on any other system:

docker pull ghcr.io/caddybuilds/caddy-bunny:latest

Building Your Own Docker Image

If you prefer to build your own Docker image, follow these steps:

Prerequisites

• GitHub account
• DockerHub account (if you wish to push the image to DockerHub as well)
• GitHub Secrets configured:
  • GITHUB_TOKEN (automatically available in GitHub Actions)
  • DOCKERHUB_USERNAME (optional, if you want to push to DockerHub)
  • DOCKERHUB_TOKEN (optional, if you want to push to DockerHub)
  • DOCKERHUB_REPOSITORY_NAME (optional, can be set as a repository secret or variable to customize the target DockerHub repository)

Setup Instructions

1. Fork this repository to your GitHub account.

2. Set up GitHub Secrets:

   • Go to your repository on GitHub.
   • Navigate to Settings > Secrets and variables > Actions.
   • Add the following secrets:
     • GITHUB_TOKEN: This is automatically available in GitHub Actions.
     • DOCKERHUB_USERNAME: Your DockerHub username (optional).
     • DOCKERHUB_TOKEN: Your DockerHub access token (optional).
     • DOCKERHUB_REPOSITORY_NAME (optional, can be set as a repository secret or variable to customize the target DockerHub repository)

3. Manually trigger the workflow (optional):

   • Go to the Actions tab in your GitHub repository.
   • Select the Build and Push Docker Image workflow.
   • Click the Run workflow button to trigger the build process manually.

4. Enable the workflow:

   • Make sure GitHub Actions is enabled for your repository. Go to the Actions tab and, if prompted, click "I understand my workflows, go ahead and enable them" to activate Actions for your fork.

5. Monitor the workflow:

   • You can monitor the progress and logs of the workflow in the Actions tab of your GitHub repository.

6. Docker image:

   • Once the workflow completes successfully, the Docker image will be available in the GitHub Container Registry under your repository.
   • You can pull the image using:

     docker pull ghcr.io/YOUR_GITHUB_USERNAME/YOUR_GITHUB_REPOSITORY_NAME:latest

Usage

You can use the built Docker image in your projects. Here is an example of how to use it in a docker-compose.yml file:

services:
  caddy:
    image: ghcr.io/YOUR_GITHUB_USERNAME/YOUR_GITHUB_REPOSITORY_NAME:latest
    restart: unless-stopped
    cap_add:
      - NET_ADMIN
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - $PWD/Caddyfile:/etc/caddy/Caddyfile
      - $PWD/site:/srv
      - caddy_data:/data
      - caddy_config:/config
    environment:
      - BUNNY_API_KEY=your_bunny_api_key

volumes:
  caddy_data:
    external: true
  caddy_config:

Defining the data volume as external makes sure docker-compose down does not delete the volume. You may need to create it manually using docker volume create caddy_data.

Replace YOUR_GITHUB_USERNAME with your GitHub username and your_bunny_api_key with your actual Bunny API key.

Contributing

Feel free to open issues or submit pull requests if you have any improvements or bug fixes.

License

This project is licensed under the MIT License. See the LICENSE file for details.