What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hello! I’m trying to migrate spryker project from 2020.09 to 2021.08 release. Currently, I’m experie

U01DE320SN6
U01DE320SN6 Posts: 37 🧑🏻‍🚀 - Cadet
edited May 2022 in Docker

Hello! I’m trying to migrate spryker project from 2020.09 to 2021.08 release. Currently, I’m experiencing some issue trying to build Yves frontend:

╰─$ console frontend:project:cleanup-dependencies && console frontend:project:install-dependencies
Store: DE | Environment: docker.dev
Cleanup frontend project dependencies
Store: DE | Environment: docker.dev
Install Project dependencies
╭─/data | Store: DE | Env: docker.dev | Debug: (.) | Testing: (.)
╰─$ console frontend:yves:install-dependencies
Store: DE | Environment: docker.dev
Install Yves dependencies
╭─/data | Store: DE | Env: docker.dev | Debug: (.) | Testing: (.)
╰─$ console frontend:yves:build
Store: DE | Environment: docker.dev
Build Yves frontend



  yves

Attempting to build Zed fails with some issue as well:

╰─$ console frontend:zed:build
Store: DE | Environment: docker.dev
Build Zed frontend



  zed

A bit confused on what do I have to do next now, so some advice would be helpful.

Comments

  • U019JM2HE7N
    U019JM2HE7N Posts: 61 🧑🏻‍🚀 - Cadet

    Probably node_modules are missing in your container. Try running docker/sdk cli npm ci first

  • U01DE320SN6
    U01DE320SN6 Posts: 37 🧑🏻‍🚀 - Cadet

    Hmm, it looks like there’s no python3 in my container:

    npm ERR! code 1
    npm ERR! path /data/node_modules/node-sass
    npm ERR! command failed
    npm ERR! command sh -c node scripts/build.js
    npm ERR! Building: /usr/bin/node /data/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
    npm ERR! gyp info it worked if it ends with ok
    npm ERR! gyp verb cli [
    npm ERR! gyp verb cli   '/usr/bin/node',
    npm ERR! gyp verb cli   '/data/node_modules/node-gyp/bin/node-gyp.js',
    npm ERR! gyp verb cli   'rebuild',
    npm ERR! gyp verb cli   '--verbose',
    npm ERR! gyp verb cli   '--libsass_ext=',
    npm ERR! gyp verb cli   '--libsass_cflags=',
    npm ERR! gyp verb cli   '--libsass_ldflags=',
    npm ERR! gyp verb cli   '--libsass_library='
    npm ERR! gyp verb cli ]
    npm ERR! gyp info using node-gyp@3.8.0
    npm ERR! gyp info using node@16.14.2 | linux | x64
    npm ERR! gyp verb command rebuild []
    npm ERR! gyp verb command clean []
    npm ERR! gyp verb clean removing "build" directory
    npm ERR! gyp verb command configure []
    npm ERR! gyp verb check python checking for Python executable "/usr/bin/python3" in the PATH
    npm ERR! gyp verb `which` failed Error: not found: /usr/bin/python3
    
  • U01DE320SN6
    U01DE320SN6 Posts: 37 🧑🏻‍🚀 - Cadet

    Okay, makes sense. That’s probably because we migrated our docker image to spryker/php:80-alpine3.15

  • U01DE320SN6
    U01DE320SN6 Posts: 37 🧑🏻‍🚀 - Cadet

    Weird, another day I performed the same installation on alpine3.15 image, and frontend build worked with no issues

  • U01DE320SN6
    U01DE320SN6 Posts: 37 🧑🏻‍🚀 - Cadet

    So might be some temporary issue