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

Fixes: Building docker in Virtualbox fails #2976

Closed
wants to merge 1 commit into from
Closed

Fixes: Building docker in Virtualbox fails #2976

wants to merge 1 commit into from

Conversation

chilicat
Copy link

@chilicat chilicat commented Dec 1, 2013

Building docker in virtualbox fails since the machine has not enough memory.

Error:

sudo docker run -privileged -v `pwd`:/go/src/github.com/dotcloud/docker docker 

---> Making bundle: binary (in bundles/0.7.0-dev/binary)
# github.com/dotcloud/docker/docker
collect2: ld terminated with signal 9 [Killed]

Building docker in virtualbox fails since the machine has not enough memory. 

Error: 
```
sudo docker run -privileged -v `pwd`:/go/src/github.com/dotcloud/docker docker 

---> Making bundle: binary (in bundles/0.7.0-dev/binary)
# github.com/dotcloud/docker/docker
collect2: ld terminated with signal 9 [Killed]
```
@pnasrat
Copy link
Contributor

pnasrat commented Dec 1, 2013

That's probably a little to high for some folks. What is the amount of memory you got by default. I've successfully built with the default Vagrantfile config which gives you 364M IIRC.

If we're changing this (I've sometimes needed to for building with -race, I'd personally prefer support passing it in from ENV somehow rather than hard coding a large number. /cc @mzdaniel

@creack
Copy link
Contributor

creack commented Dec 2, 2013

/cc @mzdaniel

@crosbymichael
Copy link
Contributor

@unclejack can you take a look at this?

@unclejack
Copy link
Contributor

@chilicat A requirement of 2 GB of RAM for the virtual machine is too much for many people. Let's see what can be done to build Docker in VirtualBox without increasing the limit up to 2 GB.

I'll look into this and leave this PR open to serve as an issue which tracks the problem.

@pnasrat
Copy link
Contributor

pnasrat commented Dec 4, 2013

@chilicat did this happen on a clean build of the vagrant box with no other containers in?

vagrant destroy
vagrant up && sleep 120 && vagrant reload
vagrant ssh

Then in the virtual box.

cd /vagrant
make build

@chilicat
Copy link
Author

chilicat commented Dec 5, 2013

Made another test and you guys are right, 512 MB (which is also the default) is enough to build docker.
Most likely I had another container running inside the machine.

@chilicat chilicat closed this Dec 5, 2013
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

Successfully merging this pull request may close these issues.

None yet

5 participants