Check your docker-compose file
Paste or drop a docker-compose.yml or compose.yaml. It is read in this tab only and never uploaded, so the passwords in it stay with you. You get what will break and what is risky, each with a one-line fix and its source, and for 100 known apps the data folders their docs say must be mounted. Only have a docker run line from a README? Convert it to a compose file first.
Why a generic validator, or a chat, misses what matters here
- Your file holds your passwords. Compose files routinely carry database passwords and API keys. Pasting one into a chat or an upload-based validator hands them to a third party. This page parses the file with a YAML library served from this site and shows any secret-looking value as its first two characters and
•••, in the page and in the Markdown export. - It knows where 100 apps keep their data. Syntax checkers see a valid file when Immich runs without its
/datamount. Dankhost holds each app's documented services, images, volumes and variables, copied from the app's own docs, so it can tell you that your photos, your Vaultwarden vault or your Paperless documents live inside the container and disappear at the next update. - It fills in your variables the way Compose does, without seeing them. Add your
.envand every$VARand${VAR}in the file is resolved by the rules of the Compose interpolation reference:${VAR:-default}uses the default when VAR is unset or empty,${VAR-default}only when it is unset,${VAR:?error}and${VAR?error}stopdocker compose up,${VAR:+alt}and${VAR+alt}give the alternative only when VAR is set, and$$is a literal$. The.envis read with Compose's .env syntax: comments,export, single quotes kept literal, double quotes with\nescapes, and#after a space as a comment. You see which variable Compose would replace with a blank string (the warning The "X" variable is not set. Defaulting to a blank string), which is set but empty, which would stop the start, and which .env lines nothing uses, with the nearest used name when it is a likely typo. Values are shown only as their first two characters and•••(nothing at all under six characters) plus their length, in the page and in the Markdown export, and image tags are checked as they resolve. - It knows why a published database is worse than it looks. Docker publishes ports with its own firewall rules, which take effect before ufw's, so
5432:5432on a VPS is open to the internet even whenufw statussays it is denied.
What it checks
Sixteen generic rules run on every service. Each links to the Compose file reference or to Docker's own documentation.
- error The file is not valid YAML. Docker Compose refuses a file it cannot parse, so nothing in it starts. Compose file reference
- error No services, or a service that is not a mapping. A Compose file needs a top-level services: mapping, and each service must be a mapping of keys such as image: and ports:. Compose file reference: services
- error Database or cache port published on every network interface. Docker routes published ports in its own iptables rules, before ufw's rules see the traffic, so a database published as 5432:5432 on a VPS is reachable from the internet even with ufw set to deny. Docker docs: Packet filtering and firewalls, Docker and ufw
- warning Image tag is latest, or missing (which means latest). The next docker compose pull fetches whatever is newest, including a major version that migrates or breaks your data, and afterwards you cannot tell which version you were running. Compose file reference: image
- warning No restart policy. The default policy is no: after a crash, or after the server reboots, the container stays stopped until you start it by hand. Compose file reference: restart
- warning Docker socket mounted into the container. Whoever can talk to the Docker API controls the host: it can start a privileged container that mounts /. Mounting the socket :ro does not help, because read-only applies to the file, not to the API calls sent through it. Docker docs: Docker daemon attack surface
- warning privileged: true. The container gets every Linux capability and access to all host devices, so an attacker who breaks into the app has the host. Docker docs: Runtime privilege and Linux capabilities
- warning network_mode: host. The container shares the host's network: every port it listens on is open on the host, its ports: list is ignored, and it cannot reach other services by name on the file's networks. Compose file reference: network_mode
- warning cap_add: ALL, SYS_ADMIN or SYS_MODULE. ALL grants every capability; SYS_ADMIN alone covers mounting filesystems and much of what privileged mode allows; SYS_MODULE loads and unloads kernel modules, code that runs in the host's own kernel. Docker docs: Running containers, Runtime privilege and Linux capabilities
- warning Secret written in plain text in the file. Anyone who can read the file, its git history, a backup or a paste of it has the value, and docker inspect prints it. Docker docs: Manage secrets securely in Docker Compose
- error Two services publish the same host port. Only one container can bind a host port; the second fails to start with 'port is already allocated'. Compose file reference: ports
- error The whole host filesystem (/) is bind-mounted. The container can read every file on the host, including /etc/shadow and SSH keys, and change them unless the mount is read-only. Docker docs: Bind mounts
- warning A whole home directory is bind-mounted. The container can read (and, unless :ro, change) SSH keys, shell start-up files and every other file in that home, which is a short step to running code as that user. Docker docs: Bind mounts
- error depends_on names a service that is not in the file. docker compose up stops before starting anything when depends_on points at an undefined service. Compose file reference: depends_on
- error Two services use the same container_name. Container names are unique on a Docker host, so the second container cannot be created. Compose file reference: container_name
- info The top-level version: key is obsolete. Compose ignores it apart from printing a warning; it always validates against the newest schema. Compose file reference: Version top-level element (obsolete)
App-aware rules
When a service's image is one of the documented images below, five more rules compare it with that app's documented definition and cite the app's own install page. Shared images such as postgres, mariadb, redis and valkey are never taken as a sign of any app.
- error A documented data folder of a recognised app is not mounted. Whatever the app writes there lives in the container's own layer, so it is lost when the container is recreated, which docker compose pull followed by up -d does on every update.
- info A documented cache folder of a recognised app is not mounted. Nothing irreplaceable is lost, but the app rebuilds or downloads it again after every recreate.
- info The documented library folder of a recognised app is not mounted. This is where the app's docs put your own files (media, books, music). If you mount them at another path, point the app's library setting there instead.
- warning Environment variables of the documented definition are missing. The app's documented definition sets these; without them it may fall back to a default database password, a wrong public URL or untrusted proxy headers.
- info A repackaged image of a known app. Repackaged images (LinuxServer.io's, for example) often use other paths and variables than the documented image, so the app-aware checks were not run on this service.
With a .env: six more rules
These run only when you add a .env or an env_file: file; a compose file checked alone gets exactly the rules above.
- error A required variable would stop docker compose up.
${VAR:?message}stops Compose when VAR is unset or empty,${VAR?message}when it is unset, with the error required variable VAR is missing a value: message. Compose file reference: Interpolation - warning A variable the file uses is not set. An unset
${VAR}with no default becomes a blank string, with only a warning, so a database can start with an empty password or an image with an empty tag. Compose file reference: Interpolation - warning A variable is set but empty, and its use has no default for that.
VAR=counts as set:${VAR}and${VAR-default}both give a blank string; only${VAR:-default}falls back to the default. Compose file reference: Interpolation - warning A .env line or a ${...} Compose cannot read. A line that is not KEY=VALUE or a quote that is never closed sets nothing; a
${without its}makes Compose refuse the file. Docker docs: .env file syntax - info A .env variable nothing in the file uses. A
.envonly fills in${...}in the compose file; a name one or two letters away from a used one is usually a typo, and the page names the used one.COMPOSE_*andDOCKER_*variables are read by Compose itself and are not reported. Docker docs: Interpolation - info An env_file: was not given. Files you drop are matched to
env_file:entries by file name; an entry with no matching file is named, and its service's variables are not checked. When every file of a service is given, the app-aware missing-variable rule runs on it again. Compose file reference: env_file
What it cannot do
- It runs nothing. No container is started, so it cannot tell you whether an image exists, whether a tag has been published or whether the app starts.
- It checks no network. It does not look up hostnames, test ports or see your firewall; the published-port rules read only what the file says.
- It scans no CVEs. It does not pull images or look at what is inside them. Use an image scanner for that.
- It reads only the files you give it.
extends:andinclude:are not followed, so services and variables that come from another compose file are not seen. A service whoseenv_file:you did not drop gets no missing-variable check. - It cannot see your shell. Compose also takes variables from the shell you run it in (
export DB_PASSWORD=..., or--env-file). A web page cannot read those, so a variable you only export in your shell is reported as not set. - It does not evaluate profiles. Services under
profiles:are checked as if they always start, and their variables count as used. - It only knows 100 apps. App-aware findings exist only for the apps below, matched by image. Any other service still gets every generic rule.
The 100 apps it recognises, and by which images
- Nextcloud
nextcloud - Immich
ghcr.io/immich-app/immich-serverghcr.io/immich-app/immich-machine-learningghcr.io/immich-app/postgres - Jellyfin
jellyfin/jellyfin - Vaultwarden
vaultwarden/server - Home Assistant
ghcr.io/home-assistant/home-assistant - Paperless-ngx
ghcr.io/paperless-ngx/paperless-ngx - Uptime Kuma
louislam/uptime-kuma - Audiobookshelf
ghcr.io/advplyr/audiobookshelf - Navidrome
deluan/navidrome - FreshRSS
freshrss/freshrss - Forgejo
codeberg.org/forgejo/forgejo - Mealie
ghcr.io/mealie-recipes/mealie - Actual Budget
actualbudget/actual-server - Stirling-PDF
docker.stirlingpdf.com/stirlingtools/stirling-pdf - linkding
sissbruecker/linkding - Miniflux
miniflux/miniflux - Grafana
grafana/grafana-enterprise - PhotoPrism
photoprism/photoprism - Kavita
jvmilazz0/kavita - Syncthing
syncthing/syncthing - n8n
n8nio/n8n - Open WebUI
ollama/ollamaghcr.io/open-webui/open-webui - Ghost
ghost - BookStack
lscr.io/linuxserver/bookstack - Wiki.js
ghcr.io/requarks/wiki - Memos
neosmemo/memos - ntfy
binwiederhier/ntfy - Vikunja
vikunja/vikunja - Gotify
gotify/server - changedetection.io
ghcr.io/dgtlmoon/changedetection.io - Authelia
authelia/authelia - AdGuard Home
adguard/adguardhome - wg-easy
ghcr.io/wg-easy/wg-easy - Frigate
ghcr.io/blakeblackshear/frigate - Firefly III
fireflyiii/core - Tandoor Recipes
vabene1111/recipes - Grocy
lscr.io/linuxserver/grocy - Homepage
ghcr.io/gethomepage/homepage - Kopia
kopia/kopia - Portainer CE
portainer/portainer-ce - Pi-hole
pihole/pihole - Plex Media Server
plexinc/pms-docker - Node-RED
nodered/node-red - Mosquitto
eclipse-mosquitto - Zigbee2MQTT
ghcr.io/koenkk/zigbee2mqtt - Umami
ghcr.io/umami-software/umami - Calibre-Web
lscr.io/linuxserver/calibre-web - Gitea
docker.gitea.com/gitea - Dozzle
amir20/dozzle - Homarr
ghcr.io/homarr-labs/homarr - SearXNG
searxng/searxng - code-server
codercom/code-server - PrivateBin
privatebin/nginx-fpm-alpine - authentik
ghcr.io/goauthentik/server - Radicale
ghcr.io/kozea/radicale - Karakeep
ghcr.io/karakeep-app/karakeepghcr.io/karakeep-app/karakeep-chrome - wallabag
wallabag/wallabag - IT-Tools
corentinth/it-tools - HedgeDoc
quay.io/hedgedoc/hedgedoc - Seerr
ghcr.io/seerr-team/seerr - SiYuan
b3log/siyuan - Reactive Resume
amruthpillai/reactive-resume - ToolJet
tooljet/tooljet - Appsmith
appsmith/appsmith-ce - Trilium Notes
triliumnext/trilium - Khoj
pgvector/pgvectorghcr.io/khoj-ai/terrariumghcr.io/khoj-ai/khoj - Glance
glanceapp/glance - QwenPaw
agentscope/qwenpaw - Langfuse
docker.langfuse.com/langfuse/langfuse-workerdocker.langfuse.com/langfuse/langfusecgr.dev/chainguard/minio - Plausible CE
ghcr.io/plausible/community-edition - ArchiveBox
archivebox/archivebox - Dashy
lissy93/dashy - Beszel
henrygd/beszel - NocoBase
nocobase/nocobase - listmonk
listmonk/listmonk - Neko
ghcr.io/m1k1o/neko/firefox - Linkwarden
ghcr.io/linkwarden/linkwarden - ConvertX
ghcr.io/c4illin/convertx - DocuSeal
docuseal/docuseal - BentoPDF
ghcr.io/alam00000/bentopdf-simple - Termix
ghcr.io/lukegus/termixguacamole/guacd - Documenso
documenso/documenso - MeTube
ghcr.io/alexta69/metube - TREK
mauriceboe/trek - RomM
rommapp/romm - PLANKA
ghcr.io/plankanban/planka - Gatus
twinproduction/gatus - Homer
b4bz/homer - Owncast
owncast/owncast - Dawarich
freikin/dawarich - OmniTools
iib0011/omni-tools - LibrePhotos
reallibrephotos/librephotosreallibrephotos/librephotos-frontendreallibrephotos/librephotos-proxypgautoupgrade/pgautoupgrade - Homebox
ghcr.io/sysadminsmedia/homebox - Photoview
photoview/photoview - SparkyFitness
codewithcj/sparkyfitnesscodewithcj/sparkyfitness_server - bitmagnet
ghcr.io/bitmagnet-io/bitmagnet - 13ft
ghcr.io/wasi-master/13ft - Moodist
ghcr.io/remvze/moodist - OliveTin
jamesread/olivetin - AdventureLog
ghcr.io/seanmorley15/adventurelog