New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permission denied when running the executable it installed #100
Comments
Hi! sorry I missed this one. can I ask you how is |
Same thing. But when running $ whalebrew /usr/local/bin/rush --version
bash: /usr/local/bin/rush: Permission denied
$ sudo whalebrew /usr/local/bin/rush --version
0.5.8
$ ls -l /usr/local/bin/{whale,rush}*
-rwxr-xr-x 1 root root 64 Oct 16 13:59 /usr/local/bin/rush
-rwxrwxrwx 1 root root 15958371 Oct 16 13:44 /usr/local/bin/whalebrew Note that I am testing it with whalebrew 0.2.3, since 0.2.4 does not work. |
ok, I think I understand what is happening in other words, your
This will have the effect to disable the default option to keep the current user ID: Line 78 in 3158fcd
|
I don' understand - why are you modifying container users in the first place?
If it runs with "docker run..." it should run with whalebrew. |
The purpose of running as user is to solve the problem of writing to files.
When you install any package on your system, later, when you run the command as any user, you expect the command to be run as your user. Here Whalebrew has, by default, the same behaviour. A large proportion of the packages actually needs to access and write files on the filesystem, which, in case this flag is not set, issues like #40 or #11 . There are though, as you pointed, some packages for which the user ID they set is important. They are, from my experience, mostly packages that does not need to access the file system. For those, whalebrew has the |
Thanks. I am closing this. For my needs, any of the below two approaches is probably more suitable: alias rush="docker run -it --rm dannyben/rush" or, to create a file #!/usr/bin/env bash
docker run -it --rm dannyben/rush |
Hi.
Running on Ubuntu 18, I get permission denied errors, not sure why.
Here is what I do and what I tested.
I found a couple of duplicate issues, but they were closed and from 2017.
The text was updated successfully, but these errors were encountered: