FAQ

This is a list of questions and answers to rake-compiler-dock. You're welcome to add your own questions, when you've found suitable answers.

rake-compiler-dock related

Q: Why on hell should I use a Virtual Machine running Linux to build Windows gems?

A: For gem authors primary working on OS-X or Linux, this allows to build ready-to-run binary gems for Windows in a reproducible way, without digging too much into development on Windows. It is also often less fragile to deliver binary gems, because the Windows build environment is not as much standardized as on Linux.

Q: How can I build signed gems?

A: Copy certificate and key into the container through the current working directory. Here is an example: https://github.com/ged/ruby-pg/blob/master/Rakefile.cross#L287

boot2docker related

Q: docker version complains about "certificate is valid for 127.0.0.1, 10.0.2.15, not 192.168.59.107"

A: This is probably due to a bug in boot2docker-1.7.0 . Use one of the fixes in #issue-824 .

Q: rake-compiler-dock ls -l shows an empty directory, but it isn't on the host

A: rake-compiler-dock can only mount local drives - network drives can not be used as working directory.

Q: rake-compiler-dock fails on boot2docker start and boot2docker delete doesn't help.

A: boot2docker init creates a VM in Virtualbox. Try to start the VM within the VirtualBox GUI. This can give an indication, why the VM can not be started.

Q: The boot2docker VM is started within the VirtualBox GUI, but boot2docker start still fails.

A: It could disturb boot2docker, if there are some ancient versions of MSYS tools are in the search path. Try boot2docker start -v to get some debug information what fails.

Docker related