https://github.com/roboconf/rabbitmq-with-ssl-in-docker

RabbitMQ and SSL made easy for tests
https://github.com/roboconf/rabbitmq-with-ssl-in-docker

docker docker-image rabbitmq ssl tls

Last synced: 3 months ago
JSON representation

RabbitMQ and SSL made easy for tests

• Host: GitHub
• URL: https://github.com/roboconf/rabbitmq-with-ssl-in-docker
• Owner: roboconf
• Created: 2017-05-10T17:43:58.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2017-05-10T18:01:30.000Z (over 7 years ago)
• Last Synced: 2023-08-13T03:10:29.678Z (over 1 year ago)
• Topics: docker, docker-image, rabbitmq, ssl, tls
• Language: Shell
• Size: 12.7 KB
• Stars: 32
• Watchers: 5
• Forks: 27
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# RabbitMQ with SSL Configuration in Docker

> RabbitMQ and SSL made easy for tests.

[![Build Status](https://travis-ci.org/roboconf/rabbitmq-with-ssl-in-docker.svg?branch=master)](https://travis-ci.org/roboconf/rabbitmq-with-ssl-in-docker)

[![License](https://img.shields.io/hexpm/l/plug.svg)](http://www.apache.org/licenses/LICENSE-2.0)

This repository aims at building a RabbitMQ container with SSL enabled.  

Generation of the server certificates, as well as server configuration, are performed during

the image's build. A client certificate is generated when a container is created from this image.

It is recommended to mount a volume so that the client certificate can be reached from the

host system. Client certificates are generated under the **/home/client** directory.

## To build this image

```

cd tests && ./build.sh

```

The generated image contains SSL certificates for the server side.

## To run this image

```

mkdir -p /tmp/docker-test \

	&& rm -rf /tmp/docker-test/* \

	&& docker run -d --rm -p 12000:5671 -v /tmp/docker-test:/home/client rabbitmq-with-ssl:latest

```

Here, we bind the port 5671 from the container on the 12000 port on the local host.  

We also share a local directory with the container, to retrieve the client certificate.

You can verify client certificates were generated with `ls /tmp/docker-test`. This directory contains

a key store and a trust store, both in the PKCS12 format.

## To stop the container

`docker stop ` will stop the container.  

If you kept the `--rm` option, it will be deleted directly.

## To run quick tests

```

cd tests && ./test.sh

```

## To diagnose troubles

* Verify the client certificates were correctly generated: `ls -l /tmp/docker-test`

* Inspect the container: `docker exec -ti  /bin/bash`

* Check the logs: `docker logs `

* Verify the SSL connection works: `openssl s_client -connect 127.0.0.1:12000 -key /tmp/docker-test/key.pem`  

This last command will result in `Verify return code: 19 (self signed certificate in certificate chain)`, which is normal.

We should specify the **-CApath**, which is inside the Docker container. This test is enough to verify SSL is enabled and

the server is reachable from the host system.

## Quick overview of the content

* **Dockerfile**: the file with instructions to create a Docker image.

* **rabbitmq.config**: the configuration file for RabbitMQ.

* **openssl.cnf**: a configuration file used during certificates creation.

* **prepare-server.sh**: a script during the generation of the image and that deals with server certificates.

* **generate-client-keys.sh**: a script that is run by default when a container is created from this image.

It deals with the generation of client certificates.