Greegrass V2 Component Deployment Issue.

Question

Hi Team,

I have created one ReactJS application and deployed in Greengrass V2 using component recipe with following details.

"Lifecycle": {
        "Install": {
          "RequiresPrivilege": true,
          "Script": "yarn install --cwd {artifacts:decompressedPath}/softacuity-code",
          "Timeout": 6000
        },
        "Run": {
          "Script": "chmod 777 {artifacts:decompressedPath}/softacuity-code/node_modules 
 npm start --prefix {artifacts:decompressedPath}/softacuity-code"
        }
      },
      "Artifacts": [
        {
          "Uri": "s3://elsa-component-artifacts/FrontEndManager/customer_board/softacuity-code.zip",
          "Digest": "iPUASOImWCUL/IsSPJdO1MMVHF9XfKH52GdtafoExtU=",
          "Algorithm": "SHA-256",
          "Unarchive": "ZIP",
          "Permission": {
            "Read": "ALL",
            "Execute": "ALL"
          }
        }

I am successfully able to deploy this component on greengrass v2.  But second time if i try to deploy any other component in revise deployment I am getting following error.
**unable to access attributes of symbolic link**

**Caused by: java.nio.file.FileSystemException: /greengrass/v2/packages/artifacts-unarchived/CSTBOARDFrontEndManager/3.0.0/softacuity-code/node_modules/@eslint/eslintrc/node_modules/.bin/js-yaml: Too many levels of symbolic links or unable to access attributes of symbolic link
        at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:96)
        at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
**

Could you guys please help me with this. Is there anything required to be updated in recipe file ??

Regards,
Nalay Patel

Accepted Answer

Hi,

it is hard to tell the issue you are facing without seeing the code. You might have some recursion in your symbolic links.

I would anyway not recommend to deploy and run React application in the way you are doing. It is better to build the application with `npm run build` and then ship the build folder that can be served via web server like `live-server` (ONLY for development) or NGINX.

Check also [this article](https://repost.aws/articles/ARFNdB78ErSTSlxPOz4cl-HA) I just published.

Cheers,

Massimiliano

Greegrass V2 Component Deployment Issue.

Relevanter Inhalt