You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FROM node:20.11.0
RUN npm install -g @microsoft/rush
WORKDIR /app
COPY . .
RUN sh ./scripts/presetup-rush.sh
RUN sh ./scripts/build.sh
RUN sh ./scripts/create-workspace.sh
EXPOSE 3000
CMD ["rush", "docker:up"]
Expected behaviour
The app to be up and running
Actual behaviour
=> ERROR [5/7] RUN sh ./scripts/presetup-rush.sh
[5/7] RUN sh ./scripts/presetup-rush.sh:
0.935 sh: 0: cannot open ./scripts/presetup-rush.sh: No such file
Dockerfile:49
47 |
48 | # Exécuter les scripts de pré-configuration et d'installation
49 | >>> RUN sh ./scripts/presetup-rush.sh
50 |
51 | # Exécuter les commandes rush nécessaires
ERROR: failed to solve: process "/bin/sh -c sh ./scripts/presetup-rush.sh" did not complete successfully: exit code: 2
@Bae360
You are creating a separate Dockerfile if that dockerfile is in the root directory then it should only use /scripts/presetup-rush.sh similar for other script files too
This reads as a support question about a custom Docker build rather than a code defect or a concrete feature request. It may be better suited to the community channels or documentation. If maintainers agree, please consider closing.
@Bae360 — as explained above, this does not look like something that can be addressed in the codebase. Could you please close this issue if you agree? If you think there is a code change needed after all, please describe what should change.
Activity
namanvats commentedon Jun 12, 2024
@Bae360
You are creating a separate Dockerfile if that dockerfile is in the root directory then it should only use
/scripts/presetup-rush.shsimilar for other script files tooMichaelUray commentedon Oct 20, 2026
This reads as a support question about a custom Docker build rather than a code defect or a concrete feature request. It may be better suited to the community channels or documentation. If maintainers agree, please consider closing.
MichaelUray commentedon Oct 20, 2026
@Bae360 — as explained above, this does not look like something that can be addressed in the codebase. Could you please close this issue if you agree? If you think there is a code change needed after all, please describe what should change.