-
Notifications
You must be signed in to change notification settings - Fork 584
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
Getting "Permission denied" when running Electron apps with --no-sandbox #3883
Comments
It should work if you add |
Thank you! So the solution until firejail v >=0.9.65 hits the Debian backports repos seems to be: running If you know of a (similar but) better / hardened solution (like keeping apparmor in that profile and only removing that noexec part) until that occurs please leave comment, closing this. |
In Debian (in other OS it might be firejail-local) this should work and seems to be the better solution:
The problem with that is that I get: |
If you want to ignore apparmor on all profiles that include electron.profile,
Then you could just run it like this:
Or, if you want to use a separate profile for the programs in
Run it with:
|
How can one run Electron apps that use a new version of Electron with Firejail?
This works:
/home/username/Downloads/dir/appName --no-sandbox
This doesn't:
firejail --profile=/etc/firejail/electron.profile /home/username/Downloads/dir/appName --no-sandbox
The output is:
(Moved it to ~/Downloads/dir to prevent
No such file or directory
errors.)sudo less /var/log/syslog | grep appName
shows:I also tried it with
--ignore=disable-mnt --ignore=nodbus
System: Debian 10/KDE
Firejail version: 0.9.64 (with /etc/firejail/electron.profile of that version)
Some electron apps work even without setting --no-sandbox so it's probably already solved/solvable somehow.
Possibly related issues (will remove the links if not found to be related later): #3586 #3871 #2690 #2946
The text was updated successfully, but these errors were encountered: