These versions of Vagrant are officially supported by this plugin:
2.2.4
2.2.9
2.2.10
2.2.14
These Vagrant versions are NOT supported:
NOTE: The reason is they require special patches and this is not the goal of this plugin to solve upstream issues here. However, we will triage and help contribute fixes to upstream dependencies as we have spare time but we also appreciate help traige and fixes as well if you have time.
2.2.5
2.2.6
2.2.7
2.2.11
2.2.12
2.2.13
This is a bug fix release when provisioning docker hosts inside of vagrant. This version removes the hard coded DOCKER_CONFIG environment variable in /etc/environment and hard codes the client config to /home/vagrant/.docker/config.json. This is a temporary work around until the this can be refactored.
Existing values in /home/vagrant/.docker/config.json should be preserved and merged when the vagrant-proxy conf is being provisioned.
A release tagging error caused this release to become a draft release and this will be re-released as 2.0.10.
This is a bug fix release for windows users which fixes a bug with the tempfile creation when uploading and downloading files from the vagrant machine.
Big thanks to @chucknelson for debugging and troubleshooting and getting to the bottom of this for windows users. Thank you!
- @chucknelson
This is a bug fix release.
- Addresses issues with docker proxy configuration and permissions.
Thank you to these folks how identified the bugs and provided workarounds.
- @antoinetran
- @tkang007
This is a bug fix release addressing a permissions problem with the docker proxy client config. The fixes the permissions problem setting /etc/docker/config.json from 0600 to 0644 permissions.
- Credit to this release goes to @takuto-h.
- Dropped support for vagrant 1.9.8 due to our tests failinging and it's more than 2 years old.
- Credit to this release goes to @greut. Thank you for your detailed information and for reporting a solution.
This is a feature enhancement for the APT proxy configuration when using a proxy that is terminating SSL. By default, these settings are left as-is and only enabled when a user wants to configure these settings. This feature supports enabling/disabling the follwoing settings
Acquire::https::Verify-Host
Acquire::https::Verify-Peer
- The value for these settings must be a string.
- When
"true"
enable the setting - When
"false"
disable the setting - When
""
this setting is removed.
Vagrant.configure("2") do |config|
config.vm.define 'apt_host' do |c|
c.vm.box = "bento/ubuntu-18.04"
if Vagrant.has_plugin?('vagrant-proxyconf')
c.proxy.http = ENV['HTTP_PROXY']
c.proxy.https = ENV['HTTPS_PROXY']
c.proxy.no_proxy = ENV['NO_PROXY']
c.apt_proxy.verify_host = "false"
c.apt_proxy.verify_peer = "false"
c.proxy.enabled = {
:apt => {
:enabled => true,
:skip => false,
},
:env => {
:enabled => true,
:skip => false,
},
:git => {
:enabled => true,
:skip => false,
}
}
end
end
end
export VAGRANT_APT_VERIFY_HOST="false"
export VAGRANT_APT_VERIFY_PEER="false"
vagrant up
vagrant provision
NOTE If you change a setting in your Vagrantfile
and the box is
running, you can run vagrant provision
or vagrant reload
to adjust
the settings.
Supporting Issues:
Supporting Integration Tests:
- Look at the examples in directory 199
This is a bug fix release to address a logic issue for supporting docker versions when attempting to configure a docker proxy.
Bug Fixes:
This is a bug fix release to address systemd and docker issues.
Bug Fixes:
This is a bug fix release, please see the issues below for furthe details. This fix should address some Docker proxy problems when using systemd.
Bug Fixes:
Improvements:
- Check for existence of HTTP_PROXY and HTTPS_PROXY environment variables. If neither are set this plugin is automatically disabled.
- Correctly uses the Tempfile pattern now via commit. 8ee2a2bb146aeb9fb1b27c80814e9000eff34aa1
Bug fixes:
- Docker proxy conf not set the first time the provisioner is used (trusty64) - #155
- Proxy doesn't work for Docker with systemd - #172
- Provisioning of docker fails - #180
- Docker provider: Guest-specific operations were attempted on a machine that is not ready for guest communication. - #181
- Provisioning of docker fails issue 180. - #182
- vagrant-proxyconf running on Win10 and provisioning with Docker. - #186
- Cannot force to write but without configuration. - #188
Improvements:
- Significant refactor to support disabling a proxy. Now when
config.proxy.enabled = false
all supporting proxies will be uncofigured. - Added new tests for new features.
- Updated README.md to reflect new behavior.
- Cleaned up travis builds to support newere versions of vagrant.
Features:
- Added new configuration parameter for
skipping
configuring a disabled or enabled proxy.
Bug Fixes:
- Disable proxy settings in provisioned box ([GH-167][])
- unable to disable proxy for chef provisioners ([GH-118][])
- Proxy remains enabled after updating config ([GH-87][])
Improvements:
- Support URI-encorded UserInfo for Chef, SVN, Yum (GH-130)
- Support docker on Debian/Ubuntu with systemd (GH-133)
Bug fixes:
- Fix docker configuration (GH-106)
Features:
- Ignore specific applications by passing a hash to
config.proxy.enabled
(GH-93) - Support the
chef_zero
provisioner in Vagrant 1.7+ (GH-105)
Improvements:
- Add -f option for mv and rm commands to overrides any -i or -n options in shell aliases (GH-90)
- Use system-wide configuration for NPM (GH-91)
- Avoid restarting docker when configuration doesn't change (GH-92)
- Fix Chef provisioner detection compatibility with Vagrant 1.7+ (GH-103)
Bug fixes:
- Don't error if removing non-existing git proxy configuration (GH-94)
Features:
- Support for configuring Docker (GH-69)
Improvements:
- Ensure that the .npmrc file exists to work around NPM-5065
Bug fixes:
- Fix /etc/environment for empty end
false
values
Improvements:
- Write environment variable configuration also to /etc/environment on Linux (GH-58, GH-67)
- Fixes compatibility with vagrant-omnibus and non-login shells
Features:
- Support setting proxy environment variables on Windows guests (GH-63)
- Support setting proxy environment variables on CoreOS guests (GH-62)
- Requires CoreOS 286.0 or later
Bug fixes:
- Fix https proxy configuration for npm if different to http (GH-57)
- Use absolute paths to
git
,npm
, andpear
commands when configuring them using sudo to avoid PATH problems (GH-59, GH-60)
Deprecations:
- Deprecate
config.env_proxy
andVAGRANT_ENV_*_PROXY
, asconfig.proxy.*
andVAGRANT_*_PROXY
should be enough. The env_proxy config options will be removed in v2.0.0. config.apt_proxy.*
andVAGRANT_APT_*_PROXY
URIs should explicitly set the scheme and port. In v2.0.0 the scheme will be required, and default port will be scheme's default (currently 3142).
Features:
Features:
- Add
config.proxy.enabled
option which can be set tofalse
to disable the plugin (GH-39) - Support for configuring PEAR (GH-34)
Improvements:
- Compatibility with Vagrant v1.5:
- Run Travis tests against all supported Vagrant minor versions with correct Ruby version
- Decrease noise level, don't print messages when configuring something
Bug fixes:
- Quote
no_proxy
in /etc/profile.d/proxy.sh to protect it from spaces (GH-42)
- Ensure that Yum configuration includes the (default) port (GH-36)
- Add support for configuring Yum directly (not only via global env vars) (GH-4)
- Remove the target path before uploading files to VM to avoid permission problems (GH-32)
- Disable environment variable setting on CoreOS (GH-35)
- Add support for the vagrant-vbguest plugin (GH-30)
- Compatibility with vagrant-aws v0.4.0 (GH-28)
- Next vagrant-aws release will remove its custom TimedProvision action class
- Ensure that generated configuration files are not deleted before uploading (GH-29)
- Fix sudo configuration on old Ubuntu 10.04 "lucid" guests (GH-26)
- Ubuntu bug #553786
- Always set correct permissions on generated configuration files (GH-27, GH-26)
- Configure sudo to preserve the
*_proxy
environment variables (GH-23, GH-25)- Requires that sudo in VM is configured to support "sudoers.d", i.e. /etc/sudoers contains line
#includedir /etc/sudoers.d
- Requires that sudo in VM is configured to support "sudoers.d", i.e. /etc/sudoers contains line
- Fix Chef provisioner configuration if a proxy is set to
false
(GH-24) - Create the directories for configuration files if they don't exist (GH-25)
- BREAKING: Environment variables for Apt config renamed to
VAGRANT_APT_HTTP_PROXY
etc. (GH-15) - Configure all supported programs with a single
config.proxy
configuration orVAGRANT_HTTP_PROXY
etc. environment variables (GH-14, GH-17) - Add support for global
*_proxy
environment variables viaconfig.env_proxy
(GH-6) - Configure the VM also on
vagrant provision
(GH-12)- Hook to all commands that trigger provisioning action
- Ensure the proxies are configured before vagrant-omnibus (GH-13)
- Requires vagrant-omnibus v1.1.1 or newer to work correctly
- Support the AWS provider (GH-10)
- Support
vagrant rebuild
command of the Digital Ocean provider (GH-11) - Do not add the default port to complete URIs (e.g.
http://proxy
) (GH-9)
- Add Apt proxy configuration for FTP URIs (GH-5)
- Warn and fail if Vagrant is older than v1.2.0 (GH-7)
- New home page (GH-8)
- Don't crash if there is no configuration for us in the Vagrantfiles (GH-2)
- Related Vagrant issue
- Initial release
- Support for Apt proxy configuration
- Based heavily on vagrant-cachier plugin