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 images should default to installing mongo #2654

Closed
aaronjudd opened this issue Aug 8, 2017 · 8 comments
Closed

Docker images should default to installing mongo #2654

aaronjudd opened this issue Aug 8, 2017 · 8 comments
Assignees
Labels
enhancement For issues that describe a feature that needs to be added, changed, or removed, but is not a bug

Comments

@aaronjudd
Copy link
Contributor

aaronjudd commented Aug 8, 2017

A primary purpose (or at least, nice side role) of our docker images is that they are used for demo/testing initially by many people checking out Reaction.

Reaction images should, therefore, default to providing the Mongo instance, within the build, so they can be used as standalone instances.

Ideally, if the MONGO_URLenv variable is supplied, or MONGO=false is used, then we would not provide mongo. (normal production deployments would almost always have MONGO_URL provided).

This has been implemented and reverted before, and needs to be implemented and remain as a requirement (or some variation, perhaps another new image).

@aaronjudd
Copy link
Contributor Author

See #1420

@saralouhicks
Copy link
Member

I saw this error yesterday and today when trying to use Kitematic.

kitematic-mongo-error

@aaronjudd
Copy link
Contributor Author

Merged into marketplace but still needs merging to other branches @jshimko

@jshimko
Copy link
Contributor

jshimko commented Aug 15, 2017

@aaronjudd Cherry pick PR's created for development (#2677) and master (#2678).

@aaronjudd
Copy link
Contributor Author

aaronjudd commented Aug 30, 2017

@jshimko Should we close this? I'm not sure I want to pull #2678 into master, is it important to do so? if not let's close both.

@jshimko
Copy link
Contributor

jshimko commented Aug 30, 2017

Assuming we don't want to merge those changes directly to master, yes, this is all set to close. The only reason I created #2678 was because this issue was specifically about being able to launch a container straight from Docker Hub (or with tools like Kitematic) without needing to setup/provide an external database. If that can wait until marketplace is merged, then we're good. That just means reactioncommerce/reaction:latest currently does not have Mongo installed in it until that time.

Want to make the call on that @aaronjudd?

@brent-hoover
Copy link
Collaborator

@aaronjudd @jshimko Can we close?

@brent-hoover brent-hoover added the enhancement For issues that describe a feature that needs to be added, changed, or removed, but is not a bug label Jan 3, 2018
@jshimko
Copy link
Contributor

jshimko commented Jan 3, 2018

@jshimko jshimko closed this as completed Jan 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement For issues that describe a feature that needs to be added, changed, or removed, but is not a bug
Projects
None yet
Development

No branches or pull requests

4 participants