You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using vagrant and chef-solo to setup consistent vm development environments. I need java and am using this plugin.
To improve performance of vagrant, I'm using two recommendations I found on the web:
use vagrant NFS file sharing
use vagrant-cachier plugin.
The benefit of using vagrant-cachier plugin is that your archives and packages downloaded from chef are stored in your user directory on the host system. This way, every time you 'vagrant up' a fresh system, you don't have to download everything if its sitting in your cache.
I'm told using NFS with vagrant improves performance as well and is recommended. The trouble is that when using this vagrant-cachier along with NFS, this causes the java chef recipe to fail.
The problem is that after the recipe successfully downloads the java archive into my cache directory, it tries to unpack it in the cache as well and this was failing for me with the following error message:
FATAL: Failed to extract file jdk-7u51-linux-i586.tar.gz!
After troubleshooting the issue by printing the stderr from executing tar, I see the following:
[2014-04-11T01:20:24+00:00] INFO: cmd.stderr tar: jdk1.7.0_51/man/ja_JP.UTF-8/man1/rmid.1: Cannot change ownership to uid 10, gid 143: Operation not permitted
This occurs for every file in the archive.
It seems there are two solutions to this:
In providers/ark.rb on line 154, include the "--no-same-owner" option to the tar command
Don't try to unpack the downloaded archive in the same cache directory but perhaps in /tmp on the guest system.
In my local environment I chose the first suggestion and it resolved my issue.
As I explained in a previous issue ( #163 ), I'm a chef newbie at this point and not skilled enough at this point to complete the guidelines to submit a pull request, but if this issue remains open and I become season enough in chefspec and your integration test suite, I might give it a try.
In the meantime, thanks again for the great plugin.
The text was updated successfully, but these errors were encountered:
DISCLAIMER - I'm a chef/vagrant newbie here
I'm using vagrant and chef-solo to setup consistent vm development environments. I need java and am using this plugin.
To improve performance of vagrant, I'm using two recommendations I found on the web:
The benefit of using vagrant-cachier plugin is that your archives and packages downloaded from chef are stored in your user directory on the host system. This way, every time you 'vagrant up' a fresh system, you don't have to download everything if its sitting in your cache.
I'm told using NFS with vagrant improves performance as well and is recommended. The trouble is that when using this vagrant-cachier along with NFS, this causes the java chef recipe to fail.
The problem is that after the recipe successfully downloads the java archive into my cache directory, it tries to unpack it in the cache as well and this was failing for me with the following error message:
After troubleshooting the issue by printing the stderr from executing tar, I see the following:
This occurs for every file in the archive.
It seems there are two solutions to this:
In my local environment I chose the first suggestion and it resolved my issue.
As I explained in a previous issue ( #163 ), I'm a chef newbie at this point and not skilled enough at this point to complete the guidelines to submit a pull request, but if this issue remains open and I become season enough in chefspec and your integration test suite, I might give it a try.
In the meantime, thanks again for the great plugin.
The text was updated successfully, but these errors were encountered: