> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/developer-tools-and-resources/dev-environments-and-faqs/building-from-pre-build-containers.md).

# How to build from pre-built containers?

#### Docker compose configuration for apple M1 using images:

```
version: "3.8"
services:
  mongo:
    image: mongo
    command: "--setParameter allowDiskUseByDefault=true"
    restart: always
    expose:
      - 27017
 
  message-broker:
    image: nats:2.10.9
    expose:
      - 4222
    ports:
      - '8222:8222'
    command: '--http_port 8222'

  mongo-express:
    image: mongo-express:1.0.0-alpha.4
    ports:
      - 8081
    environment:
      ME_CONFIG_MONGODB_SERVER: mongo
      ME_CONFIG_MONGODB_PORT: 27017
      ME_CONFIG_SITE_BASEURL: /mongo-admin
    depends_on:
      - mongo


  notification-service:
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    image: gcr.io/hedera-registry/notification-service:2.22.0
    platform: linux/amd64
    depends_on:
      - message-broker

 
  logger-service:
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    image: gcr.io/hedera-registry/logger-service:2.22.0
    platform: linux/amd64
    depends_on:
      - message-broker
 
  worker-service-1:
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    image: gcr.io/hedera-registry/worker-service:2.22.0
    platform: linux/amd64
    depends_on:
      - auth-service
    environment:
      SERVICE_CHANNEL: 'worker.1'
      IPFS_STORAGE_API_KEY: "..."
 
  worker-service-2:
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    image: gcr.io/hedera-registry/worker-service:2.22.0
    platform: linux/amd64
    depends_on:
      - auth-service
    environment:
      SERVICE_CHANNEL: 'worker.2'
      IPFS_STORAGE_API_KEY: "..."
 
  auth-service:
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    image: gcr.io/hedera-registry/auth-service:2.22.0
    platform: linux/amd64
    depends_on:
      - mongo
      - message-broker
      - logger-service
 
  api-gateway:
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    image: gcr.io/hedera-registry/api-gateway:2.22.0
    platform: linux/amd64
    expose:
      - 3002
    depends_on:
      - mongo
      - message-broker
      - guardian-service
      - auth-service
      - logger-service
 
  policy-service:
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    image: gcr.io/hedera-registry/policy-service:2.22.0
    platform: linux/amd64
    depends_on:
      - mongo
      - message-broker
      - auth-service
      - logger-service
      
  mrv-sender:
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    image: gcr.io/hedera-registry/mrv-sender:2.22.0
    platform: linux/amd64
  
  topic-viewer:
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    image: gcr.io/hedera-registry/mrv-sender:2.22.0
    platform: linux/amd64
  
  guardian-service:
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    image: gcr.io/hedera-registry/guardian-service:2.22.0
    platform: linux/amd64
    depends_on:
      - mongo
      - message-broker
      - auth-service
      - logger-service
      - worker-service-1
      - worker-service-2
      - policy-service
    environment:
      OPERATOR_ID: "..."
      OPERATOR_KEY: "..."
      
  
  web-proxy:
    image: gcr.io/hedera-registry/frontend:2.22.0
    platform: linux/amd64
    environment:
      GATEWAY_HOST: 'api-gateway'
      GATEWAY_PORT: '3002'
      GATEWAY_CLIENT_MAX_BODY_SIZE: '1024m'
    ports:
      - "3000:80"
    depends_on:
      - guardian-service
      - auth-service
      - api-gateway
      - mrv-sender
      - mongo-express
volumes:
  mongo:
  # volume-guardian-service:
  # volume-ui-service:
  # volume-mrv-sender:
  #  volume-message-broker:
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guardian.hedera.com/docs/develop/developer-tools-and-resources/dev-environments-and-faqs/building-from-pre-build-containers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
