Skip to content
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

Automate docker image publishing #18

Open
mumoshu opened this issue May 23, 2018 · 1 comment
Open

Automate docker image publishing #18

mumoshu opened this issue May 23, 2018 · 1 comment
Assignees

Comments

@mumoshu
Copy link
Collaborator

mumoshu commented May 23, 2018

#17 added Dockerfile which is capable of building custom filebeat image, based of elastic.co/filebeat image, along with awsbeat.

I'd love it if any new tag results in a docker image automatically pubished to dockerhub. Probably we can do that with the script deploy provider.

@s12v Would you mind setting it up?
If you're short on time, I can write .traivls.yml. Then all we need is your DOCKER_USER and DOCKER_PASSWORD within travis env for docker login.

@mumoshu
Copy link
Collaborator Author

mumoshu commented May 24, 2018

I considered docker repository named s12v/awsbeats. However it seems like we will outgrow it after adding support for other beats.

Suppose we have supports for filebeat and metricbeat, we could differentiate them like

  • s12v/awsbeats:filebeat-canary and s12v/awsbeats:metricbeat-canary

vs

  • s12v/awsbeats-filebeat:canary and s12v/awsbeats-metricbeat:canary

Hopefully we have a dedicated docker org. for awsbeats so that the images look ilke:

  • awsbeats/filebeat:canary and awsbeats/metricbeat:canary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants