b24johka commented

Collaborator

For some reason the app crashes due to not having priviledges to create directory, we can resolve this by changing the priviledges of the frontend directory. However, that is just a temporary fix and we need somehow make the script to create the frontend directory with the right priviledges from the installation script.

![image](/attachments/1025b61a-cf14-4fb1-af19-7eaefc2b4f14) For some reason the app crashes due to not having priviledges to create directory, we can resolve this by changing the priviledges of the frontend directory. However, that is just a temporary fix and we need somehow make the script to create the frontend directory with the right priviledges from the installation script.

image.png

66 KiB

b24johka added the

bug

label

2026-05-07 06:35:42 +00:00

a24julot commented

2026-05-07 07:55:16 +00:00

Collaborator

Has anyone else experienced this issue?

a24hirsa commented

2026-05-07 08:24:02 +00:00

Collaborator

I can not recreate this issue on the team1_week5 branch, i've tried running npm start as a admin and non admin and it works with no visible defects or bugs for both
.

I can not recreate this issue on the team1_week5 branch, i've tried running npm start as a admin and non admin and it works with no visible defects or bugs for both .

b23albst commented

2026-05-07 09:21:59 +00:00

Collaborator

This happens to me every time I clone the repo and run the install script. I use ubuntu

a24julot commented

2026-05-07 09:29:12 +00:00

Collaborator

@b23albst wrote in #791 (comment):

This happens to me every time I clone the repo and run the install script. I use ubuntu

How did you fix it? Do we need to add something to the script?

@b23albst wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/791#issuecomment-8575: > This happens to me every time I clone the repo and run the install script. I use ubuntu How did you fix it? Do we need to add something to the script?

b24johka commented

2026-05-07 09:34:02 +00:00

Author

Collaborator

The fix is to do chown MY_USER frontend
Which is the Unix command to change the ownership folder frontend to the user being specified.
Unsure why the directory isnt being created with ownership to the user from the installation script.

The fix is to do **chown MY_USER frontend** Which is the Unix command to change the ownership folder frontend to the user being specified. Unsure why the directory isnt being created with ownership to the user from the installation script.

b24johka commented

2026-05-07 09:35:41 +00:00

Author

Collaborator

This might be a Linux only problem, we dont know really. And as previously stated, to recreate this issue you have to make clone the repository from scratch.

b23albst commented

2026-05-07 09:48:29 +00:00

Collaborator

I think more specifically the fix is to change the ownership of frontend/node_modules. This directory is created by the "npm install" command in the installation script and has root as owner (I'm guessing since install script is run with sudo). However, this might just be something specific to some versions/distros (I have ubuntu 22.04) since not every linux user has this problem

b24johka was assigned by a24julot

2026-05-07 09:59:53 +00:00

b24johka commented

2026-05-07 10:25:33 +00:00

Author

Collaborator

So i did multiple tests and found out that there might just be some lack of experience from using Linux (From my side atleast).
I am unsure why this bug appeared for the first time for me yesterday, maybe i was just lucky with my usage.

Recreating the project with not using any sudo commands for mkdir, git clone, UnixInstallation.sh, npm start will create all files with privileges to the current user. Thus, terminating the error and the issue.

However, i am not able to run UnixRebuild.sh without sudo. (Might be because docker is installed using sudo).

I also tried creating everything from scratch only using sudo. This will actually allow for npm start without using sudo.
This works flawelessly. I cant see anywhere in installation.sh or rebuildscript.sh how sudo is being enforced in anyway.
I will try to get someone else with the same issue to try this out and see if this solves the issue.

Main takeaway: use sudo for everything or nothing. if theres a mismatch where a user tries to access root privileges we get problems.

So i did multiple tests and found out that there might just be some lack of experience from using Linux (From my side atleast). I am unsure why this bug appeared for the first time for me yesterday, maybe i was just lucky with my usage. Recreating the project with not using any sudo commands for **mkdir**, **git clone**, **UnixInstallation.sh**, **npm** start will create all files with privileges to the current user. Thus, terminating the error and the issue. ![image](/attachments/d2fad404-1008-466f-b44b-1d078d973419) However, i am not able to run **UnixRebuild.sh** without sudo. (Might be because docker is installed using sudo). I also tried creating everything from scratch only using sudo. This will actually allow for **npm start** without using sudo. This works flawelessly. I cant see anywhere in **installation.sh** or **rebuildscript.sh** how sudo is being enforced in anyway. I will try to get someone else with the same issue to try this out and see if this solves the issue. Main takeaway: use **sudo** for **everything** or **nothing**. if theres a mismatch where a user tries to access root privileges we get problems.

image.png

78 KiB

b24johka added the

needs review

label

2026-05-07 10:34:23 +00:00

b23albst was assigned by a24julot

2026-05-07 12:02:14 +00:00

b23albst commented

2026-05-07 12:16:19 +00:00

Collaborator

Review on #791

Whats done

I tested making new clones of the repo and running the install script, as well as the rebuild script with and without sudo

Tested on ubuntu

When running the install script with sudo, root becomes the owner of the directory frontend/node-modules, which means sudo is required for npm start as well.
Installing without sudo is possible and then the user becomes owner of previously mentioned directory. Then npm start can be run without sudo.
As root privileges are required by docker, sudo is required for running the rebuild script.

What needs to be done

scripts/README.md
- I suggest changing the line about the unix install script to not include sudo.
- If we want to be diligent, we could also document this problem in the script usage readme

Conclusion

Error occurs when trying to run "npm start" without being the owner of frontend/node-modules, which happens when sudo is used for the install script.

# Review on #791 ## Whats done I tested making new clones of the repo and running the install script, as well as the rebuild script with and without sudo ### Tested on ubuntu + When running the install script with sudo, root becomes the owner of the directory frontend/node-modules, which means sudo is required for npm start as well. + Installing without sudo is possible and then the user becomes owner of previously mentioned directory. Then npm start can be run without sudo. + As root privileges are required by docker, sudo is required for running the rebuild script. ## What needs to be done + scripts/README.md + I suggest changing the line about the unix install script to not include sudo. ![image](/attachments/a5d2eaa9-f46a-4c25-ba70-ee661f56fdf3) + If we want to be diligent, we could also document this problem in the script usage readme ## Conclusion + Error occurs when trying to run "npm start" without being the owner of frontend/node-modules, which happens when sudo is used for the install script.

image.png

7.8 KiB

b23albst added

reviewed

and removed

needs review

labels

2026-05-07 14:37:35 +00:00