Problem resolved. 
It is this file resolv.rb that caused the encoding problem. 
There are 3 entries in this file that need to manually reset to unicode. I 
thought there was only 1 line - where the error code said.
Anyway, why I did not have this problem before is even more puzzling.


On Tuesday, December 3, 2019 at 12:13:42 PM UTC-5, Sorcerer Stone wrote:
>
> I am using Win10 with HyperV disabled & with all the latest updates. Using 
> Vagrant to test run some simple projects. No problems (in running docker, 
> compose, etc in Vagrant). 
> I uninstalled Vagrant, VirtualBox and all related folders in Windows and 
> reinstalled Vagrant & VirtualBox again. But suddenly, I ran into unicode 
> problem.
>
> Background:
> After re-installing Vagrant (+ Virtualbox) and rebooted the OS, I ran this 
> command to install docker compose:
>
> vagrant plugin install vagrant-docker-compose
>
> It returned a list of errors relating to unicode
>
> Installing the 'vagrant-docker-compose' plugin. This can take a few 
> minutes...
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:852:in 
> `[]=': incompatible character encodings: UTF-8 and ASCII-8BIT 
> (Encoding::CompatibilityError)
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:852:in 
> `sender'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:525:in 
> `block in fetch_resource'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:1133:in 
> `block (3 levels) in resolv'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:1131:in 
> `each'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:1131:in 
> `block (2 levels) in resolv'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:1130:in 
> `each'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:1130:in 
> `block in resolv'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:1128:in 
> `each'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:1128:in 
> `resolv'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:520:in 
> `fetch_resource'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:510:in 
> `each_resource'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/resolv.rb:491:in 
> `getresource'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/rubygems/remote_fetcher.rb:105:in
>  
> `api_endpoint'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/rubygems/source.rb:47:in 
> `api_uri'
>         from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/rubygems/source.rb:183:in
>  
> `load_specs'
> ....
>
> What I did to try to resolve this problem:
> I followed the instructions from here: 
> https://github.com/xyteam/xyPlatform
>
> Near the end of the article, there is a trouble shooting section. 2nd last 
> entries on this section deals with the problem I ran into. So I edited and 
> saved line 784 in resolv.rb as described in this article. aka
>
> replace request[0,2] = [id].pack('n') to request[0,2] = [id].pack('U')
>
> I rebooted the system. Ran the above command.
> I still have the same character encoding error.
>
> Can someone please advise what other steps I need to take to fix this 
> error?
> What might have suddenly prompted this error?
> I had since then uninstalled and reinstalled both Vagrant & Virtualbox 
> (latest available versions). Same result.
>
> Thanks in advance.
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/779aec31-ae0c-420f-aa17-cf48b0e98f39%40googlegroups.com.

Reply via email to