Spryker installation is failing at Section build-static stage

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