Open trein opened 11 years ago
What are the Unix permissions for each directory?
Did you ever solve this problem? I'm having the same issue
I have got the same problem.
I am working as user: axel Permissions from my source folder, were i want to create the new railsapp drwxr-xr-x 6 axel axel 4096 Okt 31 20:41 . drwxr-xr-x 36 axel axel 4096 Okt 31 20:24 ..
ruby is installed with rvm and it is under my user folder ( /home/axel/.rvm/....)
rails new myapp works perfect, i also can add something to the gemfile and make an bundle install.
Only with the composer it fails. Error is the same like above. run bundle install --without production from "." Unfortunately, a fatal error has occurred. Please see the Bundler troubleshooting documentation at http://bit.ly/bundler-issues. Thanks! /home/axel/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/fileutils.rb:245:in `mkdir': Permission denied - /.bundle (Errno::EACCES)
Sorry for the late response. I'm owner of all directories. I don't believe it is a permissions related problem since the other approach worked correctly.
Looking at the composer.rb
code, I think it can be something related to (line 2718):
say_wizard "Installing gems. This will take a while."
if prefs.has_key? :bundle_path
run "bundle install --without production --path #{prefs[:bundle_path]}"
else
run 'bundle install --without production'
end
say_wizard "Updating gem paths."
Gem.clear_paths
@davidynamic and @AxelWalsleben: If you guys are stuck in this problem, you can use the second possible method creating an empty application root directory and then calling rails
with composer
:
$ mkdir myapp
$ cd myapp
$ rails new . -m https://raw.github.com/RailsApps/rails-composer/master/composer.rb
Cheers, --trein
@trein: The Second Method works also not.
i patched the source, that the --path at bundle install is set, but that creates the same error.
I've released a new version that eliminates the 'bundle_path' hidden preference. Let me know if the issue is resolved, please.
@DanielKehoe I tried again today after your, but same problem. So, for some reason .bundle
is being created at /
and not at the app folder. Do you have any idea why?
run bundle install --without production from "."
Unfortunately, a fatal error has occurred. Please see the Bundler troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
/Users/trein/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/fileutils.rb:245:in `mkdir': Permission denied - /.bundle (Errno::EACCES)
I had the same problem. I still don't know the reason but everything started working after running gem update
@IvanMisyats is right. Just tested here and it worked. Thanks very much. If this solution works for the other people that were having trouble with that, we can close this issue as invalid. What do you guys think?
What version of RubyGems were you using before the gem update?
gem -v
Sorry about that, but I did not check it before running gem update
. Now it is 2.1.10.
After gem update, it also works in my case.
I'll close this issue now. Please reopen if anyone is still encountering it.
Does this have to do with setting the linux home directory in ~/.profile?
fixed with this url given from ruby --debug http://stackoverflow.com/questions/9056008/installed-ruby-1-9-3-with-rvm-but-command-line-doesnt-show-ruby-v/9056395#9056395
I had this issue and similar when moving to a new server.
I had installed rvm, ruby and rails as root.
I uninstalled them and reinstalled them as my self and the errors disappeared.
[SOLVED]
just remove .bundle
directory in your application path
please reopen, this is not solved
to reproduce & verify, please run this Dockerfile docker build -t openproject:4.0 .
https://github.com/blaggacao/openproject-docker/blob/734578741e072769a83c17235c6ed9d9c22da87f/Dockerfile
here is the gem update
whats that mean.? Errno::EACCES: Permission denied - /Users/spaceodyssey/Desktop/hipster/vendor/bundle/ruby/2.0.0/gems/hitimes-1.2.2/.travis.yml
An error occurred while installing hitimes (1.2.2), and Bundler cannot continue.
Make sure that gem install hitimes -v '1.2.2'
succeeds before bundling. ?
@SpaceG you could try this
chown your_username /Users/spaceodyssey/Desktop/hipster -R
Woah that worked for me, thanks @itsNikolay
FYI the error message I was getting was from of a Snow Plow installation on an EC2 instance with Amazon Linux (https://github.com/snowplow/snowplow/wiki/1-Installing-EmrEtlRunner)
The message was:
Unfortunately, a fatal error has occurred. Please see the Bundler troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
/home/ec2-user/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/fileutils.rb:247:in `mkdir': Permission denied - /bin/snowplow/3-enrich/emr-etl-runner/.bundle (Errno::EACCES)
The command I ran to fix was :
sudo chown ec2-user /bin/snowplow/3-enrich/emr-etl-runner -R
Hmm... I thought this is about fixing, and not for providing support... my2cents
I'm leaving this issue open because it seems some developers are encountering this issue. As far as I can tell, it is a local configuration issue and there's nothing to fix in Rails Composer. As long as people are encountering the issue, it's helpful that people are offering ideas for resolution, and hopefully it will mean everyone will have success using Rails Composer.
I'm unsure of the real cause of this issue but running as sudo
works as the offending libraries are installed with root.
I faced the same problem. I'n my case i needed to run my comman from directory i've permited do "mkdir" command.
Hi.
I tried to create a new application using rails-composer, but I keep receiving a permission denied error.
However, if I follow the second method by creating an empty application root directory (commands below), it does not happen.
Reference: http://railsapps.github.io/installrubyonrails-mac.html
The error is the following: