Portainer Templates logo

Portainer Templates

CheckCle CheckCle

Stack

Monitoring

Open Source solution for seamless, real-time monitoring of full-stack systems, applications, and infrastructure. Provides deep insights across servers, applications, and services with uptime monitoring, SSL tracking, and infrastructure metrics.

Image details

Pulls: 360k
Architecture: amd64, arm64, arm64/v8
Image size: 43 MB
Latest: v1.6.0
User: operacle
Created: May 09, 2025
Updated: 11 months ago
Status: active

Source details

Repo: operacle/checkcle
Stars: 3k
Forks: 251
Language: Go
License: MIT
Latest: v1.6.0 · 11 months ago
Updated: 1 month ago
Website: checkcle.io/

Configuration

Type
Compose
Platform
linux
Image
operacle/checkcle:latest
Ports
8090:8090
Volumes
/mnt/pb_data : /portainer/Files/AppData/Config/checkcle/pb_data
Restart
unless-stopped
Source
Repo

Template by xneo1·Source

Standalone Install

Select an install method, to see config/commands for deploying CheckCle

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select CheckCle, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

version: '3.9'

services:
  checkcle:
    image: operacle/checkcle:latest
    container_name: checkcle
    restart: unless-stopped
    ports:
      - 8090:8090
    volumes:
      - /portainer/Files/AppData/Config/checkcle/pb_data:/mnt/pb_data
    ulimits:
      nofile:
        soft: 4096
        hard: 8192
    networks:
      - checkcle-network

networks:
  checkcle-network:
    driver: bridge

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/checkcle.yml up -d

More install options in our documentation, or see operacle/checkcle for app-specific guidance.

CheckCle Logo
📦 Official Docker Image of CheckCle
CheckCle is an Open Source solution for seamless, real-time monitoring of full-stack systems, applications, and infrastructure. It provides developers, sysadmins, and DevOps teams with deep insights and actionable data across every layer of their environment—whether it's servers, applications, or services. With CheckCle, you gain visibility, control, and the ability to ensure optimal performance throughout your entire technology stack.
Check more on Github: https://github.com/operacle/checkcle Follow the Quick Start Guide at https://checkcle.io

Serve CheckCle on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying checkcle.example.com to http://checkcle:8090

Add this to your Caddyfile

checkcle.example.com {
	reverse_proxy http://checkcle:8090
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:8090 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :8090
  • Stop the other service, or pick a different host port. In 8090:8090 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:8090. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, checkcle can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8090

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/checkcle/pb_data

Image won't pull

Test the pull directly on the host: docker pull operacle/checkcle:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64, arm64/v8
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

CheckCle is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

The app image

An image is the app packed up ready to go, everything CheckCle needs bundled into one download. This template pulls operacle/checkcle:latest, which Docker fetches once (about 43 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. CheckCle's comes from Docker Hub, published by operacle.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is v1.6.0. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm64/v8, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 8090:8090 means it's reachable on port 8090 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 8090:8090

Volumes

A volume is where CheckCle keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /mnt/pb_data from /portainer/Files/AppData/Config/checkcle/pb_data on the host

Restart policy

The restart policy here is unless-stopped, so Docker restarts CheckCle after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so CheckCle sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container checkcle. That's what you'll spot in the containers list and use in commands like docker logs checkcle.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Open source license

CheckCle is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set CheckCle up. Add the template list to Portainer once, then deploying CheckCle is a click rather than a wall of config.