Fixing 'no configuration file provided: not found' after migrating to Compose V2
Docker Composerevision 1
Diagnostic tree
In progressCompose V2 can't find a configuration fileCompose V2 is a `docker` CLI plugin (`docker compose`), not the old standalone `docker-compose` binary, and it is stricter about failing loudly rather than searching parent directories the way some V1 setups did.
View the whole map (8 more steps)
Is there actually a compose file in the current working directory?
Is the command run from the file's directory, with no conflicting -f pointing elsewhere?
No compose file exists under any of the four default names
Invocation and file placement look correct
The command isn't being run from where the file actually lives
Run from the right directory, or pass the file explicitly
Confirm compose finds and parses the file
Resolved
What to test
Compose V2 can't find a configuration file
Compose V2 is a `docker` CLI plugin (`docker compose`), not the old standalone `docker-compose` binary, and it is stricter about failing loudly rather than searching parent directories the way some V1 setups did.