Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

brantian commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2289277371 After a few attempts, I was able to make it work by: - Switching to the 4.0.2 tag instead of using the main branch - Running both Docker as admin -- This is an automat

Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

mistercrunch commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2278270838 I'm guessing superset-node is not done building the assets, either failed or is taking forever (?) Would look something like that -> https://github.com/user-attachments/ass

Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

brantian commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2278170810 @mistercrunch yes, I'm on Windows. I deleted the repo locally and cloned it again, and now the docker-compose startup works However, this is what I see after logging

Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

enricozab commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2277270482 @brantian I wasn't able to run it on Windows. I was able to run it on my Mac with Docker Desktop and resources settings of CPU=8core, memory/ram=8GBm, and swap=4. -- This is

Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

mistercrunch commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2276926680 Curious- @brantian are you on Windows too? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL a

Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

mistercrunch commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2267152563 Guessing that has to do with virtualization being super slow and/or swapping. 16GB should be enough. One thing to note is that this step is super IO intensive while dealing w

Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

enricozab commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2266357294 I'm using Windows 11 and Docker Desktop with WSL2. I have already set the memory to 12GB (even tried up to 16GB) but I still get stuck at that part. It doesn't crash, it's just

Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

mistercrunch commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2265848286 Does it crash/gets killed? Seems memory-related too or more inderectly swapping if it's just coming to a crawl. We'll need a way to control/diminish memory usage when b

Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

enricozab commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2265089931 I have also fixed this issue by increasing my WSL memory. However, I encounter this issue where I get stuck at "**[webpack.Progress] 94% sealing after seal**". ![image](

Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

bhavik-malhotra commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2264647387 It was indeed a memory issue, a simple fix for this that worked for me was changing the `build` variable under `scripts` in `package.json` to `"build": "export NODE_OPTION

Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

rusackas commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2263599391 This is almost certainly docker running out of memory. Try bumping it to something like 16MB and let us know if that resolves it. This is something that @mistercrunch is looking

Re: [I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

dosubot[bot] commented on issue #29825: URL: https://github.com/apache/superset/issues/29825#issuecomment-2262816294 Hey there, @bhavik-malhotra! I'm here to help you out with any bugs, questions, or contributions while waiting for a human maintainer. Let's tackle this together!

[I] failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1 [superset]

bhavik-malhotra opened a new issue, #29825: URL: https://github.com/apache/superset/issues/29825 ### Bug description I am running docker on Mac OS(M3) Cloned fresh repository. Ran the command "docker compose up" Ran into error ### How to reproduce the bug ```bash