Self-host imgproxy with Levelrail

A fast image processing server that resizes, crops and converts images on the fly from signed URLs. Apache-2.0 licensed. A signing key and salt are generated for you, so only URLs signed with them are served.

  • Authorimgproxy
  • LicenceApache-2.0
  • Memory256 MiB
  • Archarm64
  • Services1

How to self-host imgproxy

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/imgproxy/imgproxy:v4.0.20
  2. Create the app

    One service starts in a single Compose app, on port 8080.

  3. Fill in the secrets

    2 secrets are generated and stored encrypted, 3 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

imgproxy requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 image published
Ports
8080
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then imgproxy. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the imgproxy docs page.

Deploy imgproxy your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy imgproxy from the CLI

levelrail-cli templates deploy imgproxy --name my-imgproxy

Deploy imgproxy with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/imgproxy/deploy

imgproxy configuration

imgproxy services

ServiceImagePortsVolumes
imgproxy ghcr.io/imgproxy/imgproxy:v4.0.20 8080 none

imgproxy environment variables

VariableServiceValue
IMGPROXY_BIND imgproxy Preset by the template
IMGPROXY_ENABLE_DEBUG_HEADERS imgproxy Preset by the template
IMGPROXY_KEY imgproxy Generated at deploy
IMGPROXY_SALT imgproxy Generated at deploy
IMGPROXY_USE_ETAG imgproxy Preset by the template

Ports and volumes

Ports
8080
Volumes
none

imgproxy FAQ

How much memory does imgproxy need?

The catalog lists about 256 MiB of memory for imgproxy.

Does imgproxy run on arm64?

For imgproxy, an arm64 image is published; amd64 is image published.

What licence is imgproxy under?

imgproxy is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does imgproxy need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does imgproxy use?

imgproxy listens on port 8080 inside the stack.

Can I deploy imgproxy on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id imgproxy for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/imgproxy/imgproxy:v4.0.20 is what you deploy there.

levelrail-cli templates deploy imgproxy --name my-imgproxy