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

Docker Container (EJabberD and Central Agent) and (Agent) #1189

Open
bdallen opened this issue Sep 10, 2016 · 3 comments
Open

Docker Container (EJabberD and Central Agent) and (Agent) #1189

bdallen opened this issue Sep 10, 2016 · 3 comments

Comments

@bdallen
Copy link

bdallen commented Sep 10, 2016

Hi guys,

Not much of an issue, more of a feature request for myself and working on at the moment.

Has anyone actually done this already, if not i'm planning to do this into docker containers and will share the image / dockerfiles with you guys. Just wondering if there are any gotcha's or issues pertaining to getting this run in a docker image. This will make rolling out alot faster to hypervisor nodes and getting the central orchestrators running.

@primalmotion
Copy link
Member

Hi,

I'm not aware of anybody having already done this, so feel free to go ahead.

I don't see any potential issue.

You could even make a docker container for the agent, if you have some spare time :)

Thanks,

Antoine Mercadal

On Sep 9, 2016, at 7:51 PM, Brendon Allen [email protected] wrote:

Hi guys,

Not much of an issue, more of a feature request for myself and working on at the moment.

Has anyone actually done this already, if not i'm planning to do this into docker containers and will share the image / dockerfiles with you guys. Just wondering if there are any gotcha's or issues pertaining to getting this run in a docker image. This will make rolling out alot faster to hypervisor nodes and getting the central orchestrators running.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@bdallen
Copy link
Author

bdallen commented Sep 10, 2016

Sweet, will do. I notice there haven't been updates happening for a while, and development is slow. I understand that most people are working etc but is there any plans to continue development of Archipel?

@HTPC-Schrauber
Copy link
Contributor

I have made an ArchipelClient image.
It is based on nginx:alpine and therefor relatively small.

Look at here: https://hub.docker.com/r/schrauber/archipelclient/

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

3 participants