This does not seem to be a WordPress installation WordPress Origin: Application & API Last updated 14 Oct 2026

WP-CLI: Error: This does not seem to be a WordPress installation. Pass --path=`path/to/wordpress` or run `wp core download`

WP-CLI couldn’t find WordPress in the current directory (or the --path given).

Exact message you may see This does not seem to be a WordPress installationPass --path=`path/to/wordpress` or run `wp core download`
Seen on: WordPress

Meaning

Run WP-CLI from the WordPress root, or pass --path. In Bedrock/custom layouts, wp-cli.yml should point to the web/wp folder. Using sudo can change the working directory or user.

Common causes

  • Running wp from the wrong directory
  • Custom layout (Bedrock, subfolder install) without wp-cli.yml
  • wp-config.php outside the expected location

⚡ Quick fix

  1. cd to the WordPress root or use --path=/var/www/html
  2. Add wp-cli.yml with path: web/wp
  3. Run as the web user: sudo -u www-data wp …

Detailed fix by platform

Shell

  1. php
    wp --path=/var/www/html core version
    echo "path: web/wp" > wp-cli.yml

How to diagnose

  1. Directory — pwd contains wp-load.php?
  2. Layout — Bedrock/subfolder?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Application & API. Errors that are often confused with or caused by this one (click to open):

docker-compose: command not found — docker-compose: command not found / 'compose' is not a docker command (Docker)docker-compose: comma…invalid reference format — docker: invalid reference format (repository name must be lowercase) (Docker)invalid reference for…is not running — Error response from daemon: Container X is not running (Docker)is not runningNo such container — Error response from daemon: No such container (Docker)No such containerthe input device is not a TTY — the input device is not a TTY (Docker)the input device is n…There doesn't seem to be a wp-config.php file — WordPress: There doesn't seem to be a wp-config.php file. I need this before we can get started (WordPress)There doesn't seem to…You cannot remove a running container — Error response from daemon: You cannot remove a running container. Stop the container before attempting removal or force remove (Docker)You cannot remove a r…This does…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.