EACCES: permission denied

[atigm]

Commande to execute :
npm run deploy-storybook

In package.json :
"deploy-storybook": "storybook-to-aws-s3 --bucket-path=BUCKET/ --aws-profile=int"

I have this error:

+ npm run deploy-storybook

> PROJECT@0.1.7 deploy-storybook /var/jenkins_home/jobs/JOB/branches/FEATURE/workspace@2
> storybook-to-aws-s3 --bucket-path=BUCKET/ --aws-profile=int

=> Building storybook for: PROJECT
   executing: npm run build-storybook -- -o out9154

/var/jenkins_home/jobs/JOB/branches/FEATURE/workspace@2/node_modules/@storybook/storybook-deployer/src/utils.js:14
  throw new Error(
  ^

Error: Exec code(1) on executing: npm run build-storybook -- -o out9154
info @storybook/react v6.1.1
info 

info => Cleaning outputDir /var/jenkins_home/jobs/JOB/branches/FEATURE/workspace@2/out9154
ERR! Error: EACCES: permission denied, mkdir '/usr/local/bin/docker/.Trash-1000'
ERR!  [Error: EACCES: permission denied, mkdir '/usr/local/bin/docker/.Trash-1000'] {
ERR!   errno: -13,
ERR!   code: 'EACCES',
ERR!   syscall: 'mkdir',
ERR!   path: '/usr/local/bin/docker/.Trash-1000'
ERR! }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! PROJECT@0.1.7 build-storybook: `build-storybook -s public "-o" "out9154"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the PROJECT@0.1.7 build-storybook script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

I have Jenkins insalled from docker image (I insytall awscli and node)

FROM jenkinsci/blueocean
USER root
RUN apk add --no-cache \
        python3 \
        py3-pip \
    && pip3 install --upgrade pip \
    && pip3 install \
        awscli \
    && rm -rf /var/cache/apk/*

RUN apk add --update npm

USER jenkins

[sutty009]

Same issue on v6.1.1, but I use AWS Codebuild to run npm run deploy-storybook to S3.
Deployed Ok using version @storybook/react v6.0.28 a few hours before deploying again with v6.1.1 on nov 20th which failed.
Going to rollback to 6.0.28 in the mean time.

[atigm]

Thank you Sutty009

Using version 6.0.28 solved my issue.

But I leave this bug open for it to be fixed in future versions.