docker-compose error

Not specified by the original author.

Fix no configuration file provided: not found (docker-compose)

TL;DR

You ran compose from a directory that has no compose file. cd into the directory containing docker-compose.yml, or point compose at it explicitly with docker compose -f /path/to/docker-compose.yml ps. That is the whole fix.

The error, verbatim:

no configuration file provided: not found

Steps

1. Confirm you are in the wrong directory:

   pwd && ls docker-compose.yml compose.yaml 2>/dev/null

   Success check: pwd prints the directory; ls shows whether a compose file is there.

2. Change into the directory that holds the compose file:

   cd /path/to/project

   Success check: ls lists the compose file in the new directory.

3. Re-run your compose command and verify:

   docker compose ps

   Success check: Services are listed with their state; no error.

When to use

You hit this exact error while using docker-compose. The trigger list below matches your situation.

When NOT to use

If the error text differs, or the failure is in a different tool (e.g. a Docker daemon error when you only need the compose fix), find the skill for that exact error instead.

Tool compatibility

Compose v2 (docker compose) and docker-compose v1. Any OS.

Variant phrasings

no configuration file provided: not found

docker compose ps returns no configuration file provided

Root cause

Compose looks for docker-compose.yml / compose.yaml in the current working directory (or the paths given by -f / COMPOSE_FILE). When you run it from anywhere else, it finds nothing and reports this instead of guessing.

Edge cases

• Check the file is not saved with a hidden extension like docker-compose.yml.txt on Windows.
• If you use multiple files, every -f flag must point at a real file; one bad path gives the same error.
• COMPOSEFILE env var overrides the default search; an empty or wrong COMPOSEFILE causes this too.

Where this came from

Resolved from the public discussion at https://stackoverflow.com/questions/70256928 (so:70256928).

A user hit the docker-compose error "no configuration file provided: not found" (docker compose fails with no configuration file provided: not found). The accepted resolution: You ran compose from a directory that has no compose file. cd into the directory containing docker-compose.yml, or point compose at it explicitly with docker compose -f /path/to/docker-compose.yml ps. That is the whole fix. Source: https://stackoverflow.com/questions/70256928 (so:70256928).

Not specified by the original author.

Fix mapping values are not allowed here (docker-compose)

TL;DR

Your compose file has a tab character (or bad indentation) where YAML expects spaces. Search the file for tabs, replace them with spaces, and re-run. docker compose config tells you instantly whether the file parses now.

The error, verbatim:

mapping values are not allowed here

Steps

1. Find the tab characters in the compose file:

   grep -Pn "	" docker-compose.yml

   Success check: cat -A shows ^I wherever a tab hides; grep finds the lines.

2. Replace every tab with spaces (2 spaces per indent level is the compose convention):

   grep -Pn "	" docker-compose.yml

   Success check: No output means no tabs remain.

3. Validate the file parses cleanly:

   docker compose config

   Success check: The parsed file prints with no errors.

When to use

You hit this exact error while using docker-compose. The trigger list below matches your situation.

When NOT to use

If the error text differs, or the failure is in a different tool (e.g. a Docker daemon error when you only need the compose fix), find the skill for that exact error instead.

Tool compatibility

docker-compose v1 and Compose v2. Any OS; common on Windows editors.

Variant phrasings

mapping values are not allowed here

yaml: mapping values are not allowed here

Root cause

YAML forbids tab characters for indentation. A tab (or a misaligned colon, like key value value split across a line break) makes the YAML parser read a mapping where it expected a scalar, and compose surfaces the parser error. It is always a whitespace problem in the compose file, never a compose bug.

Edge cases

• A stray tab anywhere in the file breaks parsing, not just near the reported line.
• Copy-pasting from web pages can introduce non-breaking spaces that look like spaces but are not.
• After fixing, docker compose config is the fastest way to confirm the file parses.

Where this came from

Resolved from the public discussion at https://stackoverflow.com/questions/39077526 (so:39077526).

A user hit the docker-compose error "mapping values are not allowed here" (docker compose fails with mapping values are not allowed here). The accepted resolution: Your compose file has a tab character (or bad indentation) where YAML expects spaces. Search the file for tabs, replace them with spaces, and re-run. docker compose config tells you instantly whether the file parses now. Source: https://stackoverflow.com/questions/39077526 (so:39077526).

Not specified by the original author.

Fix Service "web" uses an undefined network "frontend" (docker-compose)

TL;DR

A service references a network that is not declared in the top-level networks: section. Add the network name under top-level networks: (or fix the typo), and the project validates. If the network already exists outside compose, declare it with external: true.

The error, verbatim:

Service "web" uses an undefined network "frontend"

Steps

1. Reproduce the error to see which network is undefined:

   docker compose config

   Success check: The error names the exact service and network.

2. Add the missing declaration at the top level of the compose file:

   grep -n -A3 "^networks:" docker-compose.yml

   Success check: The network name now appears under top-level networks:.

3. Re-validate and bring the stack up:

   docker compose config

   Success check: The parsed file prints with no errors.

When to use

You hit this exact error while using docker-compose. The trigger list below matches your situation.

When NOT to use

If the error text differs, or the failure is in a different tool (e.g. a Docker daemon error when you only need the compose fix), find the skill for that exact error instead.

Tool compatibility

docker-compose v1 and Compose v2. Any OS.

Variant phrasings

Service "xxx" uses an undefined network "xxx"

uses an undefined network

Root cause

A service lists a network under its networks: key, but that network is never declared in the top-level networks: section of the compose file. Compose validates references before creating anything, so one missing declaration blocks the whole project.

Edge cases

• If the network is created outside compose, declare it with external: true instead of a bare name.
• Typos are the most common cause: network names are case-sensitive.
• With multiple -f files, the top-level networks: must exist in the merged result, not just one file.

Where this came from

Resolved from the public discussion at https://stackoverflow.com/questions/52587359 (so:52587359).

A user hit the docker-compose error "Service "web" uses an undefined network "frontend"" (docker compose fails with Service uses an undefined network). The accepted resolution: A service references a network that is not declared in the top-level networks: section. Add the network name under top-level networks: (or fix the typo), and the project validates. If the network already exists outside compose, declare it with external: true. Source: https://stackoverflow.com/questions/52587359 (so:52587359).