Androids useful debugging information

Android: Refusing to read from unsafe file location
--------------------------------------------------------------
If you have files in other paths than  /mnt/sdcard
this is considered to be unsafe and Android will refuse to read it no matter if this is a video file in mp4, images in jpeg, jpg.

Have your files in /mnt/sdcard to read from .

Running Docker-machin in another location than C:/Users

In order to run docker-machine to other location than default, use the -s option or --stiorage-path as follows:

$docker-machine -s /f/.docker/machine/machines/ create --driver=virtualbox dev

However later docker runs will still point to default path, so in order to get the env to the new docker-machine you ahve to run the followinG:

$docker-machine -s /f/.docker/machine/machines/  env dev

To change default pathway to docker use :
MACHINE_STORAGE_PATH=/f/.docker/machine/machines/

You can add this in your start.sh or ~/.bashrc or in windows env variable to use the other location.

Ignore changes in tracked files using GIT

Use:
git update-index --assume-unchanged <file>

To ignore changes in tracked files.


Use:
git update-index --no-assume-unchanged <file>

If you want to check in changes in those tracked files.

Rename VM to another name

In the command line run the followinG:

$vboxmanage modifyvm ORIGNAL_NAME --name NEW_NAME

Setting up boot2docker and working with live-reload directory the easy way

Checkout https://github.com/boot2docker/boot2docker/pull/534

Download latest boot2docker from:
https://github.com/boot2docker/windows-installer/releases

If you access the boot2docker VM via the following:
$boot2docker ssh

You will not be able to have access to your host developement files. To make your
developement files accessible do the following in Windows:

$boot2docker stop
$VBoxManage.exe sharedfolder add boot2docker-vm --name Users --hostpath C:/Users --automount.



Note 1: if you are using cygwin you have to use the syntax C:/Users, not C:\Users
Note 2:

hostpath Users` share at `/Users` in the boot2docker VM

hostpath /Users` share at `/Users`  in the boot2docker VM
hostpath c/Users` share at `/c/Users`  in the boot2docker VM
hostpath /c/Users` share at `/c/Users`  in the boot2docker VM
hostpath c:/Users` share at `/c/Users`  in the boot2docker VM


$boot2docker up
$boot2docker ssh "ls /Users"

Voila!  You will see your files inside boot2docker !

But how about using another path than Users above ?
Do as follows:


$VBoxManage.exe sharedfolder add boot2docker-vm --name Afrepo --hostpath F:/gitrepositories2 --automount

$ boot2docker ssh "ls /"
You will not find your Afrepo in the list, right? Try the following:
$ boot2docker ssh "mkdir /home/docker/Afrepo && sudo mount -t vboxsf -o uid=1000,gid=50 Afrepo /home/docker/Afrepo"


You files at F:/gitrepositories2 - in your host will be accessible inside boot2docker VM and finally to your docker !

Try the following:
$ boot2docker ssh
$docker run -v /Users/...:...   if you have used Users as sharename or
$docker run -v /Afrepo/...: ...  if you have used Afrepo as sharename

Setting up Docker and Boot2docker and shared folder MAc or Windows

On Mac:

$brew install docker

$brew install boot2docker

$ boot2docker stop
$ VBoxManage sharedfolder add boot2docker-vm -name home -hostpath $HOME

$ boot2docker up
$ boot2docker ssh "sudo modprobe vboxsf && mkdir -p $HOME && sudo mount -t vboxsf home $HOME"

You can now run docker -v transparently as long as the volume is inside $HOME

More tips:http://www.incrediblemolk.com/sharing-a-windows-folder-with-the-boot2docker-vm/

https://github.com/boot2docker/boot2docker/pull/284

vagrant/machine.rb:153:in `action': wrong number of arguments (2 for 1) (ArgumentError)

Change the line from :

                  def action(name, **opts)

to:

                  def action(name, opts)

in the file located at /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/machine.rb line 153.

This will be fixed in later versions of Vagrant after 1.7.1