roribio/alpine-sqs

Need to be able to provide config files at startup.

daniel-england opened this issue · 5 comments

daniel-england commented

Need to have a way to use my config files on start up instead of editing them every time and restarting a service.

roribio commented

Hi,

Thank you for your interest :)

Could you please provide some more detail on what you're trying to accomplish?

Keep in mind that this project is only a convenience Docker implementation of the ElasticMQ project.

Thanks,
Ronald

daniel-england commented

Hi Ronald,

The only way I could find to add queues is to add them manually. It would be nice if I could pass in the elasticmq.conf and sqs-insight.conf to use when launching the container.

  • 👍1
note commented

@daniel-england I stumbled upon similar problem. According to README.md:

Alternatively, if you'd like to be able to edit configuration files locally, without having to enter the container, you can mount the configuration directory somewhere on your host directly.

docker run --name alpine-sqs -p 9324:9324 -p 9325:9325 -v /opt/alpine-sqs:/opt/config -d roribio16/alpine-sqs:latest

The problem is that it does not really work. The reason is that if I mount my directory to /opt/config on container it still gets overwritten by sqs-init.sh which does cp /opt/*.conf /opt/config/. One may think that it might work to mount to /opt instead but it does not. I don't know the semantics of mounting to already existing directories - in my case trying to do so wiped out all the existing content in container's opt which of course caused failure.

@roribio I prepared a PR that fixes that: #14

moleksyuk commented

Hi, @roribio
Yep, the same issue for me. I would like to start ElasticMQ with already predefined 2 queues, not with only default one.

roribio commented

Thanks for contributing guys, great work! 😄

  • 👍1