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? #35

Closed
CameronTStark opened this issue Oct 10, 2017 · 2 comments
Closed

Docker Container? #35

CameronTStark opened this issue Oct 10, 2017 · 2 comments

Comments

@CameronTStark
Copy link

I've gone through the installation procedure a few times and the steps seem to lend themselves nicely to making a Docker container. It would be particularly useful since it shouldn't need the the Ubuntu VM anymore and be more platform agnostic. Has anyone from your team tried this?

If not, I'd be happy to give it a shot if I can get some support on the steps it takes to set everything up.

@bemoss bemoss deleted a comment from pratapme1 Oct 11, 2017
@bemoss bemoss deleted a comment from CameronTStark Oct 11, 2017
@zxymark221
Copy link
Contributor

Great, please go ahead and test. Our team hasn't tried this before. Please let us know what support you will need.

@CameronTStark
Copy link
Author

I've done an initial trial of building a Docker container for BEMOSS3.5 but because of the GUI interface used during installation it doesn't work out of the box. I've tried to "translate" GUI/bemoss_install_v3.5.sh to a Dockerfile butthere's particulars about the install, such as the use of root, that makes doing this myself a painful trial-and-error process.

It would be easier if someone familiar with the initialization sequence could help me arrive at a distilled environment by helping me collect the following:

  • all apt-get install packages
  • all environment variables
  • pip install packages
  • non-default config files (for Cassandra, etc.)
  • startup script(s)

If there are separate processes running concurrently, and it looks like there are from the multiple terminals running after a successful install, we can create individual containers and link them together as one package. If this is the case I'd need the pip packages, apt-packages, config files, etc. separated out for each individual process running.

My hope is that this is easy, or at least isn't horrible, for people in the dev team to do; for me, I'm getting into BEMOSS and could use this functionality but I'm really focused elsewhere.

The end product would be a downloadable container that would need virtually no setup to run, be more easily customizable in a < 1GB footprint and should make adoption of BEMOSS3.5 focused on the configuration.

Can you and/or others spare the time to help me do this?

ashrafulhaque99 added a commit to ashrafulhaque99/BEMOSS3.5 that referenced this issue Apr 25, 2018
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