Replies: 2 comments
-
Hello! Yes, something in the Python Docker images changed that makes the script fail. It is reported in #3173, and there is a fix (if you want to check it out and apply it) in #3175. (It’s a simple change in Dockerfile, and an extra file called nodejs.pref.) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you. Your guidance solved the start-up issue.
…On Mon, Jan 1, 2024 at 1:24 PM Adeodato Simó ***@***.***> wrote:
Hello!
Yes, something in the Python Docker images changed that makes the script
fail. It is reported in #3173
<#3173>, and there is a
fix (if you want to check it out and apply it) in #3175
<#3175>. (It’s a simple
change in Dockerfile, and an extra file called nodejs.pref.)
—
Reply to this email directly, view it on GitHub
<#3176 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGFCJPOQK4BH5YRSNXZOZSDYML5N7AVCNFSM6AAAAABBJFUA5GVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TSOBYGQ3DE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
Newbee here. I'm in the process of setting up the dev environment on a DigitalOcean Ubuntu droplet. I'm running into an issue when I run the ./bw-dev up command. I'm getting the error: /bin/sh: 1: npm: not found at the docker startup. npm is installed on the Ubuntu environment. Before messing with the script, I'd like to know if I need to include a setting in one of the config files. Please advise.
Thanks,
Peter
Beta Was this translation helpful? Give feedback.
All reactions