[GH-ISSUE #6908] webstorm: node: Warning: an existing sandbox was detected #3413

Open
opened 2026-05-05 09:58:23 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @salisbury-espinosa on GitHub (Sep 23, 2025).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6908

WebStorm allows you to run scripts on a node internally.
When running nodejs script inside webstorm, a message pops up: Warning: an existing sandbox was detected.
Why doesn't the webstorm.profile take this into account, and are some options available for the node profile missing for WebStorm?

for example

https://github.com/netblue30/firejail/blob/master/etc/profile-m-z/nodejs-common.profile#L78

ipc-namespace

=>

dont exists in https://github.com/netblue30/firejail/blob/master/etc/profile-m-z/webstorm.profile

Originally created by @salisbury-espinosa on GitHub (Sep 23, 2025). Original GitHub issue: https://github.com/netblue30/firejail/issues/6908 WebStorm allows you to run scripts on a node internally. When running nodejs script inside webstorm, a message pops up: `Warning: an existing sandbox was detected.` Why doesn't the webstorm.profile take this into account, and are some options available for the node profile missing for WebStorm? for example https://github.com/netblue30/firejail/blob/master/etc/profile-m-z/nodejs-common.profile#L78 > ipc-namespace => dont exists in https://github.com/netblue30/firejail/blob/master/etc/profile-m-z/webstorm.profile
gitea-mirror added the
needinfo
label 2026-05-05 09:58:23 -06:00
Author
Owner

@kmk3 commented on GitHub (Sep 23, 2025):

Basic debugging information is missing; please follow the bug report template:

<!-- gh-comment-id:3324383053 --> @kmk3 commented on GitHub (Sep 23, 2025): Basic debugging information is missing; please follow the bug report template: * <https://github.com/netblue30/firejail/issues/new?template=bug_report.md>
Author
Owner

@kmk3 commented on GitHub (Sep 23, 2025):

WebStorm allows you to run scripts on a node internally.

Is it used only for running scripts or also for managing packages with npm?

Why doesn't the webstorm.profile take this into account, and are some options
available for the node profile missing for WebStorm?

Parts of nodejs-common.profile could be split into an allow-nodejs.inc profile
(as with allow-java.inc, etc).

<!-- gh-comment-id:3324384105 --> @kmk3 commented on GitHub (Sep 23, 2025): > WebStorm allows you to run scripts on a node internally. Is it used only for running scripts or also for managing packages with npm? > Why doesn't the webstorm.profile take this into account, and are some options > available for the node profile missing for WebStorm? Parts of nodejs-common.profile could be split into an allow-nodejs.inc profile (as with allow-java.inc, etc).
Author
Owner

@salisbury-espinosa commented on GitHub (Sep 24, 2025):

WebStorm allows you to run scripts on a node internally.

Is it used only for running scripts or also for managing packages with npm?

And scripts from package.json and npm install.
There's a convenient tool for running it within the ide, eliminating the need for a console.

<!-- gh-comment-id:3327115680 --> @salisbury-espinosa commented on GitHub (Sep 24, 2025): > > WebStorm allows you to run scripts on a node internally. > > Is it used only for running scripts or also for managing packages with npm? And scripts from package.json and npm install. There's a convenient tool for running it within the ide, eliminating the need for a console.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#3413
No description provided.