Overview

Drone is a container-native continuous integration server that connects source repositories to automated build pipelines. DockerCP prepares the Drone server container with persistent data, the standard web port, generated RPC secret storage, domain-aware server settings, and HTTPS routing. A compatible Drone runner is required before pipelines can execute.

Docker image drone/drone:2
Default port 80
Deployment type docker image
Recommended resources 1 CPU · 1 GB

How deployment works in DockerCP

This template gives DockerCP the deployment metadata needed to create a service, prepare runtime variables, map persistent storage, expose the internal port, and connect a public domain with SSL when required.

  1. Create or select a project where the service belongs
  2. Review the Docker image, tag, default port, environment variables, and volume mappings
  3. Deploy the service and check logs until the application is healthy
  4. Attach a domain or subdomain when the application must be available publicly
  5. Enable HTTPS and verify the final browser response

Configuration

Environment variables

Variable Default / guidance
DRONE_RPC_SECRET change_me
DRONE_SERVER_PROTO https
DRONE_SERVER_HOST drone.example.com

Persistent volumes

Volume Mount path
drone_data /data

Commands

DockerCP handles deployment from the panel, but understanding the equivalent Docker commands helps users debug services with more confidence. 

docker pull drone/drone:2
docker ps --filter "name=drone"

docker logs --tail=100 drone

DNS and SSL checklist

Step Expected result
Add A or CNAME record The domain points to the DockerCP server or configured target
Attach domain to service The service is reachable through the selected hostname
Enable HTTPS The certificate becomes active and redirect to HTTPS can be enabled

Screenshots

Panel previews for the Drone template: how deployment, the running service, and its key details look inside DockerCP.

Drone deployment form inside the DockerCP panel
Automation workflows running on the deployed service
Public webhook URL routed through the DockerCP proxy

Troubleshoot

  • Confirm the Docker image and tag exist
  • Confirm the selected internal port matches the application port
  • Confirm required variables such as database URL, app URL, and credentials are set
  • Check service logs after the first deployment
  • Verify DNS before requesting or renewing SSL certificates