Put an optional service behind a profile.
Keep a utility service separate from a normal Compose startup.
services:
app:
image: ubuntu:20.04
profiles: ["tools"]
command: ["printf", "Utility task\n"]Expected output EXAMPLE
Utility task
Details
Requires Docker Engine and Docker Compose (the docker compose command). Run in a disposable development environment with ubuntu:20.04 available locally. See the input setup for any starting containers or files. Save as compose.yaml in an empty directory and run docker compose run --rm app. Run explicitly with docker compose --profile tools run --rm app. Explicitly targeting a profiled service also activates it.
Tested on Alpine Linux v3.24 · · Client 29.9.0; Engine 29.9.0 · Compose 5.6.0; ubuntu:20.04
Test inputs, results and environment
The exact published code ran in a dedicated Linux test container with prepared inputs. Dedicated nested Docker daemon in a privileged test helper with no host Docker socket. No application data or host directories are mounted into the example containers. The outer helper has networking disabled; the base image is preloaded. Dockerfile examples are built and run; Compose examples start real containers. Fixtures and output records are isolated from the application database. Testing covers this example and its stated checks, not every input, operating system, or runtime version. The Linux container shares its host's kernel; this is not a native Windows test.
- Architecture / host kernel
- x86_64 / 6.18.54.1-microsoft-standard-WSL2
- Snippet identity / locale
- root inside disposable Docker-in-Docker helper / C.UTF-8
- Interpreter invocation
docker compose --progress quiet run --rm -T app (tools profile)- Container image ID
sha256:aa45302a315fcbba307d6749ccbbac83af2e6f9447d6d714fce5b7b1c92b1081- Code SHA-256
374b09b3b222762917c93dce81b20ef1629f79642ae1f3b9f8296cb3691965a4- Dependencies
- Compose 5.6.0; ubuntu:20.04
Test input setup
These are the prepared inputs used by the test harness. See Details above for the prerequisites and how to run this example.
# No input files required.
Observed standard output
Utility task
Exit code: 0. Standard error: empty. Validation: Exact stdout comparison. System-dependent values above are one recorded run.
Additional assertions that passed
Checks recorded by the test harness. Where Python assertions are shown, browser cases use Playwright and simulator cases may inspect pin transitions: result.stdout is captured output, work is the temporary directory, and Path is pathlib.Path. The harness also imports json and csv.
All commands returned zero; exact output matched.