Portainer Templates logo

Portainer Templates

Chevereto Chevereto

Container

OtherToolsPhoto

Chevereto is a powerful and fast image hosting script that allows you to create your very own full featured image hosting website in just minutes. Please note that this offers only the free Chevereto version..

Image details

Pulls: 13.2M
User: nmtan
Created: Apr 15, 2017
Updated: 4 years ago
Status: active

Configuration

Type
Container
Platform
linux
Image
nmtan/chevereto:latest
Ports
7382:80/tcp
Volumes
/var/www/html/images
Env vars
PUID=1000PGID=1000CHEVERETO_DB_HOST=CHEVERETO_DB_USERNAME=CHEVERETO_DB_PASSWORD=CHEVERETO_DB_NAME=CHEVERETO_DB_PREFIX=
Restart
unless-stopped

Template by novaspirit

Notes

Template created by Pi-Hosted Series
Check our Github page: https://github.com/pi-hosted/pi-hosted

Official Webpage: https://chevereto.com/
Official Docker Documentation: https://hub.docker.com/r/nmtan/chevereto


Standalone Install

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

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 Chevereto, fill in any config options, and hit Deploy

Template Import URL

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

More install options in our documentation.

nmtan/chevereto-free - Chevereto Free Docker

Deprecation Notice

Please note that chevereto-free is now sunset and doesn't receive any security updates. Please use the latest Chevereto as provided by the official website
Chevereto can be installed via Docker as well - instruction

Serve Chevereto 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 chevereto.example.com to http://Chevereto:80

Add this to your Caddyfile

chevereto.example.com {
	reverse_proxy http://Chevereto:80
}

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 Chevereto
  • 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:7382 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :7382
  • Stop the other service, or pick a different host port. In 7382:80 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:7382. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, Chevereto can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 7382

Image won't pull

Test the pull directly on the host: docker pull nmtan/chevereto: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.

  • 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 Chevereto --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Required settings are blank

CHEVERETO_DB_HOST, CHEVERETO_DB_USERNAME, CHEVERETO_DB_PASSWORD, CHEVERETO_DB_NAME, CHEVERETO_DB_PREFIX have no default value, and Chevereto may crash or misbehave if left empty.

  • Fill them in on the deploy screen before hitting deploy.

Raise an issue

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

A single container

Chevereto runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Chevereto needs bundled into one download. This template pulls nmtan/chevereto:latest, which Docker fetches once and then starts your own copy from.

Where the image comes from

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

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. Pin a specific tag if you would rather stay on one version.

Ports

A port is the door the app answers on. A mapping like 7382:80 means it's reachable on port 7382 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:7382 in a browser. It opens:

  • 7382:80, likely the web interface

Volumes

A volume is where Chevereto 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:

  • /var/www/html/images as a volume Docker manages for you

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Chevereto takes 7 of them, and 5 need a value before it'll start properly:

  • PUID, defaults to 1000
  • PGID, defaults to 1000
  • CHEVERETO_DB_HOST, needs a value
  • CHEVERETO_DB_USERNAME, needs a value
  • CHEVERETO_DB_PASSWORD, needs a value
  • CHEVERETO_DB_NAME, needs a value
  • CHEVERETO_DB_PREFIX, needs a value

Restart policy

The restart policy here is unless-stopped, so Docker restarts Chevereto 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).

Users and permissions

The PUID and PGID settings tell it which user and group to act as on your host. Point them at your own account (find yours with id $USER) so the files it writes into your mounted folders come out owned by you rather than root.

Networking

Nothing custom is set, so Chevereto 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 Chevereto. That's what you'll spot in the containers list and use in commands like docker logs Chevereto.

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.

Portainer app templates

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