Support for APT_PROXY_URL in the packer project is very different than supporting APT_PROXY_URL in the vagrant project.
In packer this is about building the image using a proxy. In vagrant plugin this about firing up the vm and having it point to a proxy after starting. Two different things. One is for the packer maintainer to not lose their minds. The other is for the user testing new blueprints etc not to lose their minds redownloading gigabytes over and over again.
akarasulu
commented
6 years ago
Support for APT_PROXY_URL in the packer project is very different than supporting APT_PROXY_URL in the vagrant project.
In packer this is about building the image using a proxy. In vagrant plugin this about firing up the vm and having it point to a proxy after starting. Two different things. One is for the packer maintainer to not lose their minds. The other is for the user testing new blueprints etc not to lose their minds redownloading gigabytes over and over again.
Here's the issue in the vagrant project: https://github.com/subutai-io/vagrant/issues/132