Re: [mosquitto-dev] Official Docker Image

["Audet, David M" <David.Audet@xxxxxx>]

Hi Thomas and Jan-Piet,

 

Thanks for the response. Adding a volume is a great idea; I’ll take a look at other examples and try to come up with a more complete Dockerfile.

In terms of contributing this (once I have something more extendable), is the workflow to first fork the Mosquitto github repo, then submit a pull request?

 

I am also going to look into Docker Hub to see how I can go about submitting an official Mosquitto Dockerfile and created tagged images in the public registry. I will need to find out more about Docker Hub’s workflow and may need to ask more questions to the Mosquitto dev community.

 

Thanks,

 

David

 

From: <mosquitto-dev-bounces@xxxxxxxxxxx> on behalf of Thomas Kerpe <thomas@xxxxxxxxx>
Reply-To: General development discussions for the mosquitto project <mosquitto-dev@xxxxxxxxxxx>
Date: Thursday, July 21, 2016 at 8:33 AM
To: "mosquitto-dev@xxxxxxxxxxx" <mosquitto-dev@xxxxxxxxxxx>
Subject: Re: [mosquitto-dev] Official Docker Image

 

Hello David, Jan-Piet, List

a good idea. Maybe look around and learn from the errors others have done. I made a docker image for myself a while ago which is used a bit. I thought about moving to alpine or similar. First of all It's useful to expose volumes so they can easily extended. For example exposing the configuration enables it to be very flexible and even certificates for TLS can be handled in that way easily.

By the way, I had different pull requests, especially https://github.com/toke/docker-mosquitto/pull/7 is interesting as it made mosquitto to respond to signals. So feel free to look into the repository and maybe steal something.

https://github.com/toke/docker-mosquitto/blob/master/Dockerfile

https://hub.docker.com/r/toke/mosquitto/

 

Thomas

 

On 07/20/2016 11:57 PM, Audet, David M wrote:

Hi,

We are using Mosquitto and starting to use Docker for containerization of our product. After looking on Docker Hub, I have found a number of unofficial images that have been created on various base OS images.

I would like to propose that a Dockerfile is created such that a new Docker image can be built and pushed to Docker Hub, so that there is an official Docker image available to the wider community.

For instance I have created a Dockerfile to install Mosquitto 1.4.8 on top of a minimal Alpine Linux Docker image:

FROM alpine:latest

LABEL Description="Mosquitto MQTT Broker"

 

# Based on:

# https://hub.docker.com/r/najibninaba/mosquitto-docker-image/~/dockerfile/

 

# Install the latest mosquitto from the pkg repo

RUN apk --no-cache --update add mosquitto && \

    rm -rf /var/cache/apk/*

 

COPY mosquitto.conf /etc/mosquitto

 

ENTRYPOINT ["/usr/sbin/mosquitto", "-c", "/etc/mosquitto/mosquitto.conf"]

 

Is it possible to do this or something similar such that when a new version of Mosquitto is built, a new Docker image is pushed to the official Docker Hub registry?

Thanks,

David

 

_______________________________________________

mosquitto-dev mailing list

mosquitto-dev@xxxxxxxxxxx

To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/mosquitto-dev

-- 

Thomas Kerpe | Buntestraße 5 | 76131 Karlsruhe | Germany

 https://toke.de | thomas@xxxxxxxxx | +49-177-8285516

GPG: B5AD 7FCB 270D A762 46D2  A8F2 B0E6 5607 ABE5 7238