Overview

Deploy Glance with a safe starter configuration that remains editable in the service files.

Docker image glanceapp/glance:latest
Default port 8080
Deployment type docker image
Recommended resources 1 · 256 MB

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

This template does not require additional environment variables by default

Persistent volumes

Volume Mount path
glance_config /app/config

Commands

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

docker pull glanceapp/glance:latest
docker ps --filter "name=glance-dashboard"

docker logs --tail=100 glance-dashboard

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 Glance template: how deployment, the running service, and its key details look inside DockerCP.

Glance deployment form inside the DockerCP panel
Public URL served through DockerCP domain routing and SSL
Running service with domain and database state

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