Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to build web container #37

Open
LiliwoL opened this issue Dec 31, 2022 · 7 comments
Open

Unable to build web container #37

LiliwoL opened this issue Dec 31, 2022 · 7 comments

Comments

@LiliwoL
Copy link

LiliwoL commented Dec 31, 2022

Hi,

i've read closed issues about same problem, but nothing change.
Always the same during yarn -s process, i've got many unmet dependencies.

I tried to fix them manually, but nothing work that way.
Sure, it's about versions.

I'll wait the correct fix to give it another try.
Regards.

@segmentation-fault-41
Copy link

same here, a lot of warnings:

Step 5/12 : RUN yarn -s
---> Running in 8cb1b1d19e00
warning Pattern ["redux-thunk@latest"] is trying to unpack in the same destination "/usr/local/share/.cache/yarn/v6/npm-redux-thunk-2.3.0-51c2c19a185ed5187aaa9a2d08b666d0d6467622-integrity/node_modules/redux-thunk" as pattern ["redux-thunk@^2.3.0"]. This could result in non-deterministic behavior, skipping.
warning " > [email protected]" has unmet peer dependency "[email protected] - 3".
warning " > [email protected]" has unmet peer dependency "popper.js@^1.16.1".
warning " > [email protected]" has unmet peer dependency "prop-types@>=15".
warning " > @testing-library/[email protected]" has unmet peer dependency "@testing-library/dom@>=5".
The command '/bin/sh -c yarn -s' returned a non-zero code: 1

@ronit99-krsna
Copy link

Any update on this? Even I'm facing the same issue.

@dezapoe
Copy link

dezapoe commented Jun 25, 2023

i also facing this issue, is there anyone that already solve this?

@AmitGajbhare
Copy link

I am facing this problem anyone knows how to fix this issue?

=> ERROR [build 4/5] RUN yarn -s 49.9s

[build 4/5] RUN yarn -s:
#10 1.152 warning Pattern ["redux-thunk@latest"] is trying to unpack in the same destination "/usr/local/share/.cache/yarn/v6/npm-redux-thunk-2.4.2-b9d05d11994b99f7a91ea223e8b04cf0afa5ef3b-integrity/node_modules/redux-thunk" as pattern ["redux-thunk@^2.4.2"]. This could result in non-deterministic behavior, skipping.
#10 49.42 error @rollup/[email protected]: The engine "node" is incompatible with this module. Expected version ">=14.0.0". Got "13.12.0"
#10 49.42 error Found incompatible module.


executor failed running [/bin/sh -c yarn -s]: exit code: 1
ERROR: Service 'web' failed to build : Build failed

@edgardok
Copy link

edgardok commented Jul 4, 2023

here, same, tried RUN yarn cache clean --all but still the same

@TimDeanMoser
Copy link

If you open the web/Dockerfile you can remove the '-s' from the RUN yarn commands to get the full error messages. In my case those were:

  • gyp ERR! missing Python

add RUN apk add --update python make g++ && rm -rf /var/cache/apk/* before RUN yarn in the web/Dockerfile, to add python to the instance

Then in the build step, I also had the error:

  • Error: Node Sass version 7.0.0 is incompatible with ^4.0.0

Node 13 (used in Dockerfile) is only compatible with node-sass between version 4 and 5, but the application pulls 7. So edit the web/package.json node-sass version to "node-sass": "^4.0.0",

This did the trick for me to get it running. But for the long term I would recommend the developer to upgrade to a newer node version and switch from 'node-sass' to 'sass', as the former is deprecated.

@Thel0ck
Copy link

Thel0ck commented Jan 23, 2024

If you open the web/Dockerfile you can remove the '-s' from the RUN yarn commands to get the full error messages. In my case those were:

  • gyp ERR! missing Python

add RUN apk add --update python make g++ && rm -rf /var/cache/apk/* before RUN yarn in the web/Dockerfile, to add python to the instance

Then in the build step, I also had the error:

  • Error: Node Sass version 7.0.0 is incompatible with ^4.0.0

Node 13 (used in Dockerfile) is only compatible with node-sass between version 4 and 5, but the application pulls 7. So edit the web/package.json node-sass version to "node-sass": "^4.0.0",

This did the trick for me to get it running. But for the long term I would recommend the developer to upgrade to a newer node version and switch from 'node-sass' to 'sass', as the former is deprecated.

Thank you sir :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants