# Hosting endpoints in Docker Linux containers

<!-- Version variant: core_9; default: [/samples/hosting/docker/index.md](/samples/hosting/docker/index.md) -->


This sample demonstrates how to use Docker Linux containers to host NServiceBus endpoints communicating over the [RabbitMQ transport](/transports/rabbitmq/index.md). While this sample uses [Docker Compose](https://docs.docker.com/compose/) to demonstrate how to orchestrate a multi-container application, the containers are compatible with other orchestration technologies, such as [Kubernetes](https://kubernetes.io/docs/home/).

The endpoints use the [.NET SDK Container Building Tools](https://github.com/dotnet/sdk-container-builds) to enable the creation of containers via the `dotnet publish` command. See the [Microsoft tutorial](https://learn.microsoft.com/en-us/dotnet/core/docker/publish-as-container?pivots=dotnet-8-0) and [customization documentation](https://github.com/dotnet/sdk-container-builds/blob/main/docs/ContainerCustomization.md) for more details.

## Prerequisites

To containerize a .NET app using `dotnet publish`:

- **[.NET 8.0.200 SDK](https://dotnet.microsoft.com/download/dotnet/8.0)** (or higher): Check your installed SDK version with `dotnet --info`.
- **[Docker Community Edition](https://www.docker.com/products/docker-desktop)**: Ensure Docker is installed and running on your system.

## Running the sample

Running the sample involves building the container images and starting the multi-container application.

### Building container images

Build the container images by using the following command:

```
dotnet publish Docker.sln -f net10.0 --os linux --arch x64 /t:PublishContainer
```

### Starting containers

When the container images are ready, the containers can be started:

```
docker compose up -d
```

## Observing containers

Both containers log to the console. These logs can be inspected:

```
docker-compose logs sender
docker-compose logs receiver
```

### Stopping and removing containers

The containers can be stopped and removed:

```
docker-compose down
```

## Code walk-through

This sample consists of `Sender` and `Receiver` endpoints exchanging messages using the [RabbitMQ transport](/transports/rabbitmq/index.md). Each of these three components runs in a separate Docker Linux container.

### Orchestration

Endpoint container images for the `Sender` and the `Receiver` are combined with an official [RabbitMQ image](https://hub.docker.com/_/rabbitmq/) to create a multi-container application using [Docker Compose](https://docs.docker.com/compose/):

<!-- snippet: compose -->

```yml
services:
    sender:
        image: sender
        depends_on:
            rabbitmq:
                condition: service_healthy    
    receiver:
        image: receiver
        depends_on:
            rabbitmq:
                condition: service_healthy    
    rabbitmq:
        image: "rabbitmq:3-management"
        ports:
            - "15672:15672"
            - "5672:5672"
        healthcheck:
            test: rabbitmq-diagnostics check_port_connectivity
            interval: 30s
            timeout: 30s
            retries: 3
```

<!-- endsnippet -->

### Transport configuration

Endpoints configure the RabbitMQ transport to use the broker instance running in the `rabbitmq` container:

<!-- snippet: TransportConfiguration -->

```cs
var transport = new RabbitMQTransport(RoutingTopology.Conventional(QueueType.Quorum), connectionString);
```

<!-- endsnippet -->