# Public Docker images

Source : https://webgune.cloud/en-us/docs/docker-images · Mis à jour le 2026-10-27

# Public Docker images

No Git repository is needed to deploy a packaged tool. Point directly to the image on Docker Hub or GHCR. The steps are in [Deploying a Docker image](/docs/deployer-docker).

## Popular images

| Image | Use | Default port |
|-------|-------|:---:|
| `nginx:alpine` | static web server | 80 |
| `caddy:alpine` | reverse proxy with automatic HTTPS | 80 |
| `adminer:latest` | database administration interface | 8080 |
| `louislam/uptime-kuma:latest` | uptime monitoring | 3001 |
| `n8n/n8n` | workflow automation | 5678 |
| `gitea/gitea:latest` | self-hosted Git forge | 3000 |
| `wordpress:latest` | WordPress CMS | 80 |

## Configuring via environment variables

Most official images are configured entirely through environment variables, without ever editing a file:

```bash
# wordpress:latest
WORDPRESS_DB_HOST=db.<namespace>.svc.cluster.local
WORDPRESS_DB_NAME=wordpress
WORDPRESS_DB_USER=wordpress
WORDPRESS_DB_PASSWORD=change-me
```

## Persistence

By default, these images have no persistent storage: data written to the container's disk disappears on restart. Always pair them with a [managed database](/docs/bases-de-donnees) rather than relying on the service's filesystem.