-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: morphlingjs@0.1.99 postinstall: NODE_PORT=1 docker-compose build
#5
Comments
Hi ! Do you have docker and docker-compose available to your terminal? |
Yup.
|
I don't have any Windows-based computer under the hand. If someone could try and reproduce this, that'd be cool. @toumas Can you try to clone the repository and let me know what happens when you run the following: |
Hi. Running
Sorry for late reply @vroudge |
doing `NODE_PORT=1 docker-compose build` is the bash way of creating a
"local" environment variable to be used by the program in the command line
it seems to just not work on windows CLI.
try doing `SET NODE_PORT=1` and then `docker-compose build`
it might just work.
…On Thu, Nov 16, 2017 at 3:44 PM, Tuomas Ukkola ***@***.***> wrote:
Hi. Running NODE_PORT=1 docker-compose build gives me 'NODE_PORT' is not
recognized as an internal or external command, operable program or batch
file. error. So I tried replacing ${NODE_PORT} with 1 in
docker-compose.yml and tried again but got
Building web
Traceback (most recent call last):
File "docker-compose", line 6, in <module>
File "compose\cli\main.py", line 68, in main
File "compose\cli\main.py", line 121, in perform_command
File "compose\cli\main.py", line 249, in build
File "compose\project.py", line 343, in build
File "compose\service.py", line 918, in build
File "site-packages\docker\api\build.py", line 246, in build
File "site-packages\docker\utils\decorators.py", line 46, in inner
File "site-packages\docker\api\client.py", line 185, in _post
File "site-packages\requests\sessions.py", line 522, in post
File "site-packages\requests\sessions.py", line 475, in request
File "site-packages\requests\sessions.py", line 596, in send
File "site-packages\requests\adapters.py", line 423, in send
File "site-packages\requests\packages\urllib3\connectionpool.py", line 595, in urlopen
File "site-packages\requests\packages\urllib3\connectionpool.py", line 363, in _make_request
File "httplib.py", line 1042, in request
File "httplib.py", line 1082, in _send_request
File "httplib.py", line 1038, in endheaders
File "httplib.py", line 882, in _send_output
File "httplib.py", line 844, in send
File "site-packages\docker\transport\npipeconn.py", line 31, in connect
File "site-packages\docker\transport\npipesocket.py", line 22, in wrapped
File "site-packages\docker\transport\npipesocket.py", line 50, in connect
pywintypes.error: (2, 'WaitNamedPipe', 'The system cannot find the file specified.')
Failed to execute script docker-compose
Sorry for late reply @vroudge <https://github.com/vroudge>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMjZ40Ap0ADnrYbIPJ_P2vBhGxz8IAWaks5s3EpSgaJpZM4QXyiz>
.
--
Cordialement,
Pierre-Marie Achart.
|
^ What he said. |
@pmachart mind sending a PR to support this? |
So I did that but got this error this time around:
|
Thank you very much for the feedback. I believe we are almost there. You need to do the Windows equivalent of the following: In the morphling directory:
and then run the docker compose command @pmachart provided you. We will improve the Windows support in an upcoming PR as soon as possible. |
So I did
But to be honest I'm little confused how to continue from here. |
i think for this error, we can add the "cross-env" module to support Windows . |
a PR is opened to try to fix it. |
Hi there,
I'd be very interested in trying this tool out but when i run
npm i -g morphlingjs
I get an error stating that postinstall failed. I haven't useddocker
before so it could be also that.Here's npm log:
The text was updated successfully, but these errors were encountered: