Uninitialized Constant Pip #159
Comments
|
I have the same problem. This is my Vagrant file: Vagrant.configure("2") do |config|
if Vagrant.has_plugin?("vagrant-proxyconf")
config.proxy.http = "http://proxy.ir.intel.com:911/"
config.proxy.https = "https://proxy.ir.intel.com:911/"
config.proxy.no_proxy = "/var/run/docker.sock,10.237.214.139,10.237.214.141,10.237.214.149,10.237.214.247,127.0.0.1,192.168.122.1,::1,fressi1,fressi2,fressi3,intel.com,localhost"
# config.git_proxy = config.proxy
end
if Vagrant.has_plugin?("vagrant-cachier")
# Configure cached packages to be shared between instances of the same base box.
# More info on the "Usage" link above
config.cache.scope = :box
config.cache.enable :pip
# OPTIONAL: If you are using VirtualBox, you might want to use that to enable
# NFS for shared folders. This is also very useful for vagrant-libvirt if you
# want bi-directional sync
# config.cache.synced_folder_opts = {
# type: :nfs,
# The nolock option can be useful for an NFSv3 client that wants to avoid the
# NLM sideband protocol. Without this option, apt-get might hang if it tries
# to lock files needed for /var/cache/* operations. All of this can be avoided
# by using NFSv4 everywhere. Please note that the tcp option is not the default.
# mount_options: ['rw', 'vers=3', 'tcp', 'nolock']
# }
end
end |
|
Sorry, but there hasn't been a release with the changes to enable pip buckets yet as the plugin is currently looking for maintainers. If you want to help out, see #143 Cheers. |
|
I've forked the repository and kicked off my vagrant box with it, and it looks like everything actually works fine on the master branch. Pip cache buckets are created successfully and (after some back and for getting proper versions of I think the problem is just that the commits 1c3fcd2, 6deb452, 8615b74 aren't in the latest version of the plugin. If you just create a new tag (v1.3.0) everything should be resolved. |
|
I figured how to install master branch from bash. It solved this issue for me. It requires git and gem commands installed. git clone https://github.com/fgrehm/vagrant-cachier.git
cd vagrant-cachier
gem build vagrant-cachier.gemspec
gem install vagrant-cachier-*.gem |
|
@fgrehm can you release a new version please? |
|
@cenk sorry for the huge delay but I haven't used vagrant / vagrant-cachier in a long time, as I mentioned before the plugin is looking for maintainers. Unfortunately I'm unable to cut a release for something I'm unable to test 😢 |
|
ran into this as well. unfortunately I am not well versed in ruby to help. but wanted to add a +1 in case anyone was watching issues to determine interest. |
|
I have the same problem. In the interest of keeping it moving a little, here's where I got to. I use Vagrant on Windows, and have no clue about Ruby (Python, Perl, PHP sure..., but not Ruby). Install ruby to match vagrant: For me, with latest Vagrant, that was 2.2.5 32-bit Then you can get the source, and build it: which produces a .gem file, which you can then install as a Vagrant plugin: And now Vagrant doesn't just crash anymore, but I still don't get any cache files created alongside the (working) apt cache, for any of npm, pip or bower (all in use on my box). My config is: |
|
Actually, for bower and npm, it is working, but only for the vagrant user, since it uses that user's personal .cache directory. pip also caches to the user's .cache directory, but that isn't picked up by cachier. In my case, I'm using a virtualenv, so I'm probably not helping myself :-) |
|
Hey, sorry for the silence here but this project is looking for maintainers 😅 As per #193, I've added the |
I have manually enabled the
pipbucket in myVagrantfilelike so:However, this seems to be causing an error when trying to boot the guest OS. Full output below:
The text was updated successfully, but these errors were encountered: