How to use this developer tool
- Paste the requested YAML or key/value input.
- Adjust the available options for the target output.
- Select Extract Services or press Ctrl/Cmd + Enter.
- Review findings, then copy or download the result.
Docker Compose Service Extractor
Turn a Docker Compose file into a compact service inventory. The extractor lists each service with its image or build source, published ports, dependencies, profiles, and declared environment names. It is useful when reviewing an unfamiliar stack or preparing documentation. All parsing happens locally in the page, and the JSON and CSV exports contain only the summary shown in the result.
Developer Input
YAML or line inputAd space
What this developer tool does
Reads the top-level services mapping and produces one normalized record per service, including source, ports, dependencies, profiles, and environment variable names.
List and mapping forms are normalized before output. Environment values are deliberately omitted from the inventory to reduce accidental disclosure.
The result is generated locally and should be reviewed before deployment.
Example
The Sample button loads a representative input. Running it produces the same structured output displayed in the result panel, including counts and any findings.
services:
frontend:
image: example/web:2.1
ports: ["3000:3000"]
depends_on: [api]
api:
build: ./api
environment:
LOG_LEVEL: infoUse cases
- Pre-commit configuration review
- Pull request documentation
- Migration inventory preparation
- Training and troubleshooting
Tips for reliable output
- Use spaces instead of tab indentation in YAML.
- Keep multi-document separators on their own line.
- Review generated files before applying them.
- Confirm static findings with official CLI validation.
- Avoid pasting production secrets into shared devices.
Processing details
List and mapping forms are normalized before output. Environment values are deliberately omitted from the inventory to reduce accidental disclosure.
YAML anchors and Compose include/extends resolution are not expanded, so inherited properties may be absent.
Frequently asked questions
Which Docker Compose service fields are included in the extracted inventory?
The result follows the static rules described on this page. Review finding 1 in context and confirm it with the relevant Docker or Kubernetes command before deployment.
Are environment variable values exposed in the service output?
The result follows the static rules described on this page. Review finding 2 in context and confirm it with the relevant Docker or Kubernetes command before deployment.
How are build-only services shown when no image is declared?
The result follows the static rules described on this page. Review finding 3 in context and confirm it with the relevant Docker or Kubernetes command before deployment.
Does the extractor follow Compose extends or include directives?
Input is processed in your browser. The page does not make a network request with the configuration, but downloaded output and browser history should still be handled according to your security policy.
Can I export the Docker Compose service list as CSV?
The result follows the static rules described on this page. Review finding 5 in context and confirm it with the relevant Docker or Kubernetes command before deployment.