Grant ownership to the package JSON file for installation step

[SzilvasiPeter]

Motivation and Context

The change is required for local development when building docker images for testing purposes.

It fixes the #1083 issue.

Description

The npm ci is not able to run if it has no ownership over the package.json files. Similar to other COPY phase, the --chown=node:node option was added.

Contribution Checklist

• I have built and tested the code locally and in a deployed app
• For frontend changes, I have pulled the latest code from main, built the frontend, and committed all static files.
• This is a change for all users of this app. No code or asset is specific to my use case or my organization.
• I didn't break any existing functionality 😄

[RahulVadisetty91]

There is a minor redundancy in the COPY commands related to the package*.json files. Specifically, both of these lines are doing the same task. To avoid redundancy, you can remove the first COPY command because the second one already includes the chown option, which sets the correct ownership.

The corrected code block is:

COPY --chown=node:node ./frontend/package*.json ./

[SzilvasiPeter]

Is this repository is archived or not maintained anymore? This trivial change is open for more than 10 days. Should I close the PR because it seems to me that the PR will never be merged?

[SzilvasiPeter]

The redundant chown commands were removed in the 207bc6d commit.