vagrant omnibus behind proxy -
ok, i'm trying update chef-client vagrant omnibus , proxyconf. figured pull proxy proxyconf, doesn't way. here plugin list:
vagrant plugin list vagrant-login (1.0.1, system) vagrant-omnibus (1.4.1) - version constraint: 1.4.1 vagrant-proxyconf (1.3.2) - version constraint: 1.3.2 vagrant-share (1.1.0, system)
and vagrant file:
vagrant.configure(vagrantfile_api_version) |config| config.omnibus.chef_version = :latest if vagrant.has_plugin?("vagrant-proxyconf") config.proxy.http = "my proxy" config.proxy.https = "my proxy" end
when run vagrant up, machine not have updated chef-client. tried using recipe[omnibus_updater] in run list still fails because recipe failing compile failure (because of older version of chef-client, pain in butt). ideas? other creating new virtual box?
update: running in debug mode doesn't show errors using :latest. updating 11.12.8 gives below error
vagrant-omnibus: * '11.12.8' not valid version of chef.
logging vm shows $http_proxy , $https_proxy set properly. running commands on built vm works:
chef-client -v chef: 10.14.2 sudo gem update chef chef-client -v chef: 11.12.8
thing 1: :latest not error out when fails grab artifact. switching named version starts fail find artifact leads me believe isn't getting through proxy.
thing 2: think problem omnibus in windows. i've found pull may fix it? https://github.com/schisamo/vagrant-omnibus/pull/89. think plug-in isn't using settings set poxy-conf.
currently using workaround: set http proxy in windows cmd line
set http_proxy=http://username:password@proxy:port
Comments
Post a Comment