-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create an official docker image based on a well-accepted, open OS #862
Comments
@bean5 : I have set up ElastAlert for production in Centos 7, with smtp server ingrained in it. I can write a dockerfile for building elastalert over centos:7 as base image. |
@abhishekunotech I would appreciate if you can share the dockerfile for this. |
@abhishekunotech can you share your dockerfile for setting up ElastAlert in Centos 7? |
sorry guys, I lost the dockerfile for the same. I will be working on
releasing one by this weekend. My bad, sorry.
*Thanks and Regards*,
*Abhishek Aravind Kulkarni* |
*Unotech Software Pvt. Ltd ** <http://www.unotechsoft.com>*
*M*: +91 7303 495 035
*O*: +91 (22) 2687 9402
*A*: D Wing, 7th floor, 32 Corporate Avenue, Off Mahakali Caves Road,
Andheri (E), Mumbai, 400093
*W*: www.unotechsoft.com
…On Wed, Apr 19, 2017 at 9:37 AM, Bean ***@***.***> wrote:
@abhishekunotech <https://github.com/abhishekunotech> can you share your
dockerfile for setting up ElastAlert in Centos 7?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#862 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AYKtkx4le1wA03sB9NaiXJ-qlI5ggKNWks5rxYhkgaJpZM4Lg5s7>
.
--
*Disclaimer :* The contents of this e-mail and attachment(s) thereto are
confidential and intended for the named recipient(s) only. It shall not
attach any liability on the originator or Unotech Software Pvt. Ltd. or its
affiliates. Any views or opinions presented in this email are solely those
of the author and may not necessarily reflect the opinions of Unotech
Software Pvt. Ltd. or its affiliates. Any form of reproduction,
dissemination, copying, disclosure, modification, distribution and / or
publication of this message without the prior written consent of the author
of this e-mail is strictly prohibited. If you have received this email in
error please delete it and notify the sender immediately.
|
Hi! |
@krizsan that is great news! Sorry to take so long to respond. Do you think you could add it in as |
I'll leave it to someone else to pick up the torch, as I need to focus on other things. |
Piping in here. In my experience having that docker file really helps. I
prefer using that one since it is based on Alpine. Basing in Python would
also work though, I think.
…On Mon, Nov 20, 2017, 4:54 PM Pavel Strashkin ***@***.***> wrote:
@Qmando <https://github.com/qmando> @bean5 <https://github.com/bean5> is
there anything the community can help with? what about #408
<#408>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#862 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB9SJgbMPg2xhY11YOBKaLIRmJ_tmR6Nks5s4h9PgaJpZM4Lg5s7>
.
|
Breast practice is to peg to a version. For python-based projects usually to a Python base image. Many projects at this point have a slim alpine flavor. Might call that a best practice. This project still references |
https://github.com/krizsan/elastalert-docker exists, but it depends on iron/python:2 which on dockerhub doesn't like to a repository, meaning that we can't prove what is in it without manually inspection.
An official container based on this would be very helpful, more trustworthy, and more robust in environments. I build my own in a way similar to krizsan, but I base it on python:2.7.12-alpine:
Since I am new to python, I don't know a better way to reliably install requirements than to call
pip install -r requirements.txt || pip install -r requirements.txt || pip install -r requirements.txt
. Krizsan doespip install -e .
, but I found that sometimes a dependency (stomp) ended up missing in the final container.Note: #408 might help fulfill this request.
Contents of
command.sh
:The text was updated successfully, but these errors were encountered: