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

Why use VirtualBox in Docker (Experimental) implementation? #57

Closed
patakijv opened this issue Oct 24, 2016 · 1 comment
Closed

Why use VirtualBox in Docker (Experimental) implementation? #57

patakijv opened this issue Oct 24, 2016 · 1 comment

Comments

@patakijv
Copy link

Great effort with this railsbox generator. Impressive.

I am curious why in the experimental docker effort you are also still using virtualbox in the mix?
The use of docker containers should replace the need for a virtual machine, right? I see that in your main vagrantfile as you configure the containers, for each container you call another vagrantfile which sets up a virtual machine itself as it does in your standard implementation. Can you explain this?

@a-chernykh
Copy link
Owner

Yeah, I agree with what you're saying, @patakijv. Usually, a set of Dockerfiles and one docker-compose.yml to rule them all is sufficient. I don't even see why ansible should be used for such setup considering that all provisioning and configuration can be done inside Dockerfile using standard DSL. I guess, at the time when I was doing initial railsbox development, I have not had enough Docker experience, that's why it ended up being a bit over-engineered. Of course, pull requests with a proper Docker usage are always welcome :)

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