anchor.diff:          run: app
   ```
   
  +For more examples and information on using this plugin, have a look at the [docker compose plugin on GitHub](https://github.com/buildkite-plugins/docker-compose-buildkite-plugin).
  +
   ## Adding buildkite-agent to the docker group
   
   To allow buildkite-agent to use the Docker client you’ll need to ensure its user has the necessary permissions. For most platforms this means adding the `buildkite-agent` user to your system’s `docker` group, and then restarting the Buildkite Agent to ensure it is running with the correct permissions. See your platform’s [Docker installation instructions](https://docs.docker.com/installation/) for more details.
  
positive.code: 
  To run your steps in a container, we recommend using [plugins](/docs/agent/v3/plugins). If you want to use docker without plugins, see [Using Docker without plugins](/docs/builds/docker-containerized-builds#using-docker-without-plugins)
  
  At the start of your `pipeline.yml`, add a step to build an image with the docker plugin. This example prebuilds the `app` image and uploads it to a registry:
  ```
  steps:
    - name: "Docker Build"
  
negative.code: ```
  BUILDKITE_DOCKER_COMPOSE_FILE=docker-compose.buildkite.yml
  ```
  
  ## Using Docker without plugins
  
  To use plain Docker instead of Docker Compose, add the following environment variable in your build step configuration:
  
  ```
  BUILDKITE_DOCKER=true
  ```
  
  For each build job the agent will now build a Docker image and run the build step’s command inside a container.
  
  If you need, you can also specify an alternate Dockerfile:
  
  ```
  BUILDKITE_DOCKER_FILE=Dockerfile.ci
  ```
  
  