Running Boot2docker behind proxy, getting FATA[0020] Forbidden for any interaction with Docker hub -

followed instruction set proxy of boot2docker , getting following fatas, clue

fata[0020] https://index.docker.io/v1/repositories/library/busybox/images: forbidden while trying pulling images

fata[0020] error response daemon: server error: post https://index.docker.io/v1/users/: forbidden  while trying login 

fata[0000] error response daemon: https://index.docker.io/v1/search?q=ubuntu: forbidden - while searching images

updated include result of curl -v https://index.docker.io:443

* rebuilt url to: https://index.docker.io:443/ * connect() proxy 34363bd0dd54 port 8099 (#0) * trying 192.168.59.3... * adding handle: conn: 0x9adbad8 * adding handle: send: 0 * adding handle: recv: 0 * curl_addhandletopipeline: length: 1 * - conn 0 (0x9adbad8) send_pipe: 1, recv_pipe: 0 * connected 34363bd0dd54 (192.168.59.3) port 8099 (#0) * establish http proxy tunnel index.docker.io:443 > connect index.docker.io:443 http/1.1 > host: index.docker.io:443 > user-agent: curl/7.33.0 > proxy-connection: keep-alive >  < http/1.1 403 forbidden < server: squid/3.4.9 < mime-version: 1.0 < date: fri, 29 may 2015 17:56:22 gmt < content-type: text/html < content-length: 3151 < x-squid-error: err_access_denied 0 < vary: accept-language < content-language: en < x-cache: miss localhost < via: 1.1 localhost (squid/3.4.9) < connection: keep-alive <  * received http code 403 proxy after connect * connection #0 host 34363bd0dd54 left intact curl: (56) received http code 403 proxy after connect 

looks proxy issue, running proxy server on host machine, accessing its host name in boot2docker vm 's http_proxy , https_proxy butcurl host_proxy:port` works no issues

i experiencing same issue 403 error when trying lxc-docker install get.docker.com (it failed because not complete apt-get update. in case, have following setup:

• vm provider: virtualbox (ubuntu 14.04 (trusty))
• environment: vagrant
• provisioner: chef-zero (via vagrant)
• proxy: @ first had forgotten this, running apt-cacher-ng on host machine (my macbook pro) keep data downloads minimum when i'm running apt-get install on vagrant vm's. in nutshell, apt-cacher-ng sets apt mirror on mac ubuntu vm's pull packages from.

i realized apt-cacher-ng doesn't support ssl repositories (https), support normal http repositories. since docker repository uses https, had find workaround.

before fixed anything, had following in /etc/apt/apt.conf.d/10mirror file in ubuntu vm's (localip ip address of mac runs apt-cacher-ng server):

acquire::http { proxy "http://#{localip}:3142"; };

the above line means ubuntu vm's getting packages through apt-cacher-ng, failing when repository used https. adding following line beneath line, things started work normally:

acquire::https { proxy \false"; };

at point, contents of /etc/apt/apt.conf.d/10mirror follows:

acquire::http { proxy "http://#{localip}:3142"; };

acquire::https { proxy \false"; };

now, run apt-get update , docker installs , i'm normal testing. in case using vagrant set 10mirror file, here lines have in vagrantfile job:

oak.vm.provision "shell", inline: "echo 'acquire::http { proxy \"http://#{localip}:3142\"; };' > /etc/apt/apt.conf.d/10mirror"  oak.vm.provision "shell", inline: "echo 'acquire::https { proxy \"false\"; };' >> /etc/apt/apt.conf.d/10mirror";