Spryker installation is failing at Section build-static stage / dashboard

dipen.vyas

I tried to install Spryker b2b on my system. I reset the local using docker/sdk reset and tried to do fresh setup with new b2b-demo-shop code.

My installation is getting failed. I have attached screenshot. Maybe Spryker docker build is getting failed.

I tried in multiple devices and getting the same error.

profuel

It's very unfortunate, @dipen.vyas .

Default recommendation is to remove node_modules folder and rerun install.

But I suggest you to run the same command in a debug mode:

console f:p:i -vvv

And then react to the errors you encounter.

jan.holzmann

Hi @profuel and @dipen.vyas ,
i actually have the same problem.
Unfortunately, executing the command

console f:p:i -vvv

individually does not lead to an error. The command works without any error message.
It only doesn't work with a docker/sdk up.

Do you have any solutions so far? Thanks for your answer

fsmeier

Heyhey,

what about docker/sdk up -v does this give any more output?

All the best,

Florian

jan.holzmann

Hi devs,

i have a problem building my projects dicussed in here

https://forum.commercequest.space/discussion/28985/spryker-installation-is-failing-at-section-build-static-stage

But the thread was closed and i don't know why. The answer for the last question is no. 'docker/sdk up -v' doesn't show any other news.
Had someone any ideas?

fsmeier

Heyhey,

whenever sb marks a thread resolved it seems to get closed. I opened it again and merged your question.

I'll ask internally for more ideas. Will come back later to you.

All the best,

Florian

fsmeier

Another idea:

Execute npm ci inside the cli from project root folder.

jan.holzmann

Thanks for the answer.
npm ci and a manual call to console f:p:i' also runs without error. But since I'm stuck in a docker/sdk up, I'm missing all the remaining commands and containers.
If i run docker/sdk up after the manual call of docker/sdk console f:p:i or docker/sdk cli npm install it will stuck on the following part.

sven.ommer

I also got this problem on windows + wsl:

The "dashboard"-Container takes way to long with its npm.
When the commands run, sometimes i can read, that the "package.json.lock is too old" and it recreates it.

Thus none of your mentioned commands will help here :(

fsmeier

Heyhey,
do you have the latest docker-sdk (master)?

Have a look here:

https://github.com/spryker/docker-sdk/issues/520

All the best,

Florian

Salmanali Agharia

Hi Team,

I've encountered an issue while setting up a B2B Marketplace Demo Shop in my local system. docker/sdk up command doesn't gets finished and gets stuck during the dashboard setup step. I'm not sure whether mac users are also facing the same issue because I'm using Windows 11 for the setup. It hangs while executing following command :- npm install log.io pm2 -g


I've checked the dashboard's image dockerfile in the Spryker's docker/sdk github repo and found out that the node version was upgraded to version 22 (i.e node:22-alpine3.20) last month. Reference :- https://github.com/spryker/docker-sdk/pull/524 . docker/sdk up command might have worked last month because the node alpine's official image 22-alpine3.20 was not updated at that time. We already have an open github issue for the same -

https://github.com/spryker/docker-sdk/issues/533

Temporary Solution :- I've tried installation by changing node version to 18 (i.e node:18-alpine) in the dashboard dockerfile and it's working without any issues and also installation is getting completed 100% without any npm errors. But the Spryker team needs to check and fix the issue for node v22.













fsmeier

Heyhey @Salmanali Agharia ,

I merged your message with an existing thread. The team is aware of this and it was supposed to be fixed with https://github.com/spryker/docker-sdk/releases/tag/1.63.0 - Are you using the latest docker-sdk? No cached images?

Currently we try to reproduce it with the latest docker-sdk but we can not - since we "fixed" it some weeks ago we are not able to reproduce it anymore yet some users are reporting that it still exists :/

All the best,

Florian

Salmanali Agharia

Hi @fsmeier,

Yes, I'm using the latest version of Docker SDK and also Docker Client is not having any cached images. I've tried fresh installation from scratch post your message and still it stucks at npm install step :(

bunyamininan

Hello @fsmeier,

I can reproduce this error on my local machine as well. I am using Windows, and WSL 2.

My b2c demo shop installation also stuck at npm install log.io pm2 -g step.

bunyamininan

@Salmanali Agharia As a workaround, I disabled the dashboard service from the deploy file.

fsmeier

Heyhey,

please have a look at the github discussions - seems to be a WSL2 bug. A post in the wsl bug thread would be very helpful. https://github.com/microsoft/WSL/issues/7254

See also downgrade PR as intermediate solution:

https://github.com/spryker/docker-sdk/pull/535

All the best,

Florian