Comment 10 for bug 1371665

I think the main problem here is the misleading error message:

vagrant@vagrant-ubuntu-trusty-64:~$ juju deploy --repository=/vagrant/charms local:precise/ubuntu --debug
2014-09-23 08:05:52 INFO juju.cmd supercommand.go:37 running juju [1.20.7-trusty-amd64 gc]
2014-09-23 08:05:52 DEBUG juju.conn api.go:187 trying cached API connection settings
2014-09-23 08:05:52 INFO juju.conn api.go:270 connecting to API addresses: [localhost:17070 10.0.3.1:17070 10.0.2.15:17070 172.16.250.15:17070]
2014-09-23 08:05:52 INFO juju.state.api apiclient.go:242 dialing "wss://localhost:17070/environment/f44ec1be-0feb-4fa4-838d-49456888735d/api"
2014-09-23 08:05:52 INFO juju.state.api apiclient.go:176 connection established to "wss://localhost:17070/environment/f44ec1be-0feb-4fa4-838d-49456888735d/api"
2014-09-23 08:06:03 INFO juju.utils http.go:66 hostname SSL verification disabled
2014-09-23 08:06:17 ERROR juju.cmd supercommand.go:323 error uploading charm: cannot access provider storage: cannot access environment: failed verification of local provider prerequisites:
juju-local must be installed to enable the local provider:

    sudo apt-get install juju-local
vagrant@vagrant-ubuntu-trusty-64:~$ sudo apt-get install juju-local
Reading package lists... Done
Building dependency tree
Reading state information... Done
juju-local is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

There is no hint that the failure is in any way related to a "memory shortage".