Killian Kemps (https://github.com/KillianKemps) has created an awesome Docker configuration to setup a Docker environment for production purpose. Thanks to Killian it is much easier now to run PIA. A simple docker-compose up does everything and gives a running website : front-end, back-end and database.
License: GNU General Public License v3.0
I had a problem when building with docker: for PIA FRONT, a library appeared missing:
An error occured during the build:
Error: ENOENT: no such file or directory, open '/var/www/pia/node_modules/save-svg-as-png/saveSvgAsPng.js'
ENOENT: no such file or directory, open '/var/www/pia/node_modules/save-svg-as-png/saveSvgAsPng.js'
Error: ENOENT: no such file or directory, open '/var/www/pia/node_modules/save-svg-as-png/saveSvgAsPng.js'
ERROR: Service 'cnil-pia-front' failed to build: The command '/bin/sh -c npm install && cp src/environments/environment.prod.ts.example src/environments/environment.prod.ts && sed -i -e "s/version: ''/version: '$PIA_VERSION'/g" src/environments/environment.prod.ts && /var/www/pia/node_modules/@angular/cli/bin/ng build --prod --build-optimizer --sourcemaps' returned a non-zero code: 1
I had to copy saveSvgAsPng.js manually from /var/lib/docker/overlay2/l/XVUEUD2R34B5445PIEWT5WW6TJ/var/www/pia/node_modules/save-svg-as-png/lib/
to
/var/lib/docker/overlay2/l/XVUEUD2R34B5445PIEWT5WW6TJ/var/www/pia/node_modules/save-svg-as-png/,
and the rest went well!
thank you
Hi,
I get stuck at this stage, if I go out with ctl - C after a while after the reboot of the car, the container backend is constantly resting without ever leaving
LINCnil-pia-back | -- add_column(:evaluations, :global_status, :integer, {:default=>0})
LINCnil-pia-back | -> 0.0012s
LINCnil-pia-back | == 20171005214002 AddGlobalStatusToEvaluations: migrated (0.0012s) ============
LINCnil-pia-back |
LINCnil-pia-back | == 20180223064141 AddCommentToAttachment: migrating ===========================
LINCnil-pia-back | -- add_column(:attachments, :comment, :text)
LINCnil-pia-back | -> 0.0006s
LINCnil-pia-back | == 20180223064141 AddCommentToAttachment: migrated (0.0007s) ==================
LINCnil-pia-back |
LINCnil-pia-back | == 20180403152239 AddIsExampleToPias: migrating ===============================
LINCnil-pia-back | -- add_column(:pias, :is_example, :integer, {:default=>0})
LINCnil-pia-back | -> 0.0011s
LINCnil-pia-back | == 20180403152239 AddIsExampleToPias: migrated (0.0012s) ======================
LINCnil-pia-back |
LINCnil-pia-back | == 20180525222420 AddConcernedPeopleSearchedOpinionToPia: migrating ===========
LINCnil-pia-back | -- add_column(:pias, :concerned_people_searched_opinion, :boolean, {:default=>false})
LINCnil-pia-back | -> 0.0011s
LINCnil-pia-back | -- add_column(:pias, :concerned_people_searched_content, :string)
LINCnil-pia-back | -> 0.0007s
LINCnil-pia-back | == 20180525222420 AddConcernedPeopleSearchedOpinionToPia: migrated (0.0020s) ==
LINCnil-pia-back |
LINCnil-pia-back | == 20181008150745 CreateStructures: migrating =================================
LINCnil-pia-back | -- create_table(:structures)
LINCnil-pia-back | -> 0.0138s
LINCnil-pia-back | == 20181008150745 CreateStructures: migrated (0.0138s) ========================
LINCnil-pia-back |
LINCnil-pia-back | == 20181008150920 AddStructureToPia: migrating ================================
LINCnil-pia-back | -- add_reference(:pias, :structure, {:foreign_key=>true})
LINCnil-pia-back | -> 0.0065s
LINCnil-pia-back | -- add_column(:pias, :structure_name, :string)
LINCnil-pia-back | -> 0.0006s
LINCnil-pia-back | -- add_column(:pias, :structure_sector_name, :string)
LINCnil-pia-back | -> 0.0006s
LINCnil-pia-back | -- add_column(:pias, :structure_data, :jsonb)
LINCnil-pia-back | -> 0.0006s
LINCnil-pia-back | == 20181008150920 AddStructureToPia: migrated (0.0085s) =======================
LINCnil-pia-back |
LINCnil-pia-back | Running via Spring preloader in process 43
LINCnil-pia-back | WARNING: Skipping key "SECRET_KEY_BASE". Already set in ENV.
Hey, I got an error when compose up:
Hi Kosmas58,
First of all, thank you for this great work.
I have followed your W10 installation procedure and I have an issue when I try to run the container (docker-compose up):
_E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
ERROR: Service 'cnil-pia-front' failed to build: The command '/bin/sh -c apt-get update && apt-get install --no-install -recommends -y git ca-certificates wget xz-utils sudo && apt-get clean' returned a non-zero code: 100_
Can you help me ?
Thanks
Regards
Hello,
We have installed PIA-Docker and we have a problem with the installation.
If we use "RAILS_ENV test", everything works but with "RAILS_ENV production" we can't connect the Frontend and the Backend.
The database seems unavailable.
Do you know if another configuration is required to work in "Production" mode
Best regards
Hello,
I've installed pia-docker and i'm just using the front part.
However, when i'm trying to import a PIA, after selecting the zip file, nothing happend.
The only log output from LINCnil-pia-front are error about no such file '/var/www/pia/dist/pia/metrics' which is not critical.
Regards
When i change the PIA_VERSION ENV in the pia-back_service_ruby Dockerfile from 2.1.0 to 2.2.0 i get a Ruby build error:
| 18-May-2021 13:59:44 | Step 12/15 : RUN bundle install |
|---|---|
| 18-May-2021 13:59:44 | ---> Running in a9492719b727 |
| 18-May-2021 13:59:46 | Fetching gem metadata from https://rubygems.org/ |
| 18-May-2021 13:59:47 | Fetching gem metadata from https://rubygems.org/............ |
| 18-May-2021 13:59:48 | Your bundle is locked to mimemagic (0.3.3) from rubygems repository |
| 18-May-2021 13:59:48 | https://rubygems.org/ or installed locally, but that version can no longer be |
| 18-May-2021 13:59:48 | found in that source. That means the author of mimemagic (0.3.3) has removed it. |
| 18-May-2021 13:59:48 | You'll need to update your bundle to a version other than mimemagic (0.3.3) that |
| 18-May-2021 13:59:48 | hasn't been removed in order to install. |
| 18-May-2021 13:59:48 | The command '/bin/sh -c bundle install' returned a non-zero code: 7 |
| 18-May-2021 13:59:48 | [echo] Building docker image failed with exitcode 7 |
| 18-May-2021 13:59:48 | |
| 18-May-2021 13:59:48 | BUILD FAILED |
| 18-May-2021 13:59:48 | /scripts-astad/build-dockercontainer.xml:196:12: /scripts-astad/build-dockercontainer.xml:202:30: Building image failed |
| 18-May-2021 13:59:48 | |
| 18-May-2021 13:59:48 | Total time: 20.6726 seconds |
Anyone knows how to solve this?
tnx!
Hey everyone,
I have set up pia-docker with support for SSL/TLS encrypted HTTP transfer. If interested, I can contribute a little write-up on how to set up pia-docker with HTTPS.
Regards, Marcel
Running build of the front failed with:
warning Error running install script for optional dependency: "/var/www/pia/node_modules/node-sass: Command failed.
Exit code: 1
Command: node scripts/build.js
Arguments:
Directory: /var/www/pia/node_modules/node-sass
Output:
Building: /opt/node-v10.13.0-linux-x64/bin/node /var/www/pia/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ '/opt/node-v10.13.0-linux-x64/bin/node',
gyp verb cli '/var/www/pia/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli 'rebuild',
gyp verb cli '--verbose',
gyp verb cli '--libsass_ext=',
gyp verb cli '--libsass_cflags=',
gyp verb cli '--libsass_ldflags=',
gyp verb cli '--libsass_library=' ]
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing \"build\" directory
gyp verb command configure []
gyp verb check python checking for Python executable \"python2\" in the PATH
gyp verb `which` failed Error: not found: python2
gyp verb `which` failed at getNotFoundError (/var/www/pia/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/var/www/pia/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/var/www/pia/node_modules/which/which.js:80:29)
gyp verb `which` failed at /var/www/pia/node_modules/which/which.js:89:16
gyp verb `which` failed at /var/www/pia/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /var/www/pia/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb `which` failed python2 { Error: not found: python2
gyp verb `which` failed at getNotFoundError (/var/www/pia/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/var/www/pia/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/var/www/pia/node_modules/which/which.js:80:29)
gyp verb `which` failed at /var/www/pia/node_modules/which/which.js:89:16
gyp verb `which` failed at /var/www/pia/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /var/www/pia/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb `which` failed stack:
gyp verb `which` failed 'Error: not found: python2\\n at getNotFoundError (/var/www/pia/node_modules/which/which.js:13:12)\\n at F (/var/www/pia/node_modules/which/which.js:68:19)\\n at E (/var/www/pia/node_modules/which/which.js:80:29)\\n at /var/www/pia/node_modules/which/which.js:89:16\\n at /var/www/pia/node_modules/isexe/index.js:42:5\\n at /var/www/pia/node_modules/isexe/mode.js:8:5\\n at FSReqWrap.oncomplete (fs.js:154:21)',
gyp verb `which` failed code: 'ENOENT' }
gyp verb check python checking for Python executable \"python\" in the PATH
gyp verb `which` failed Error: not found: python
gyp verb `which` failed at getNotFoundError (/var/www/pia/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/var/www/pia/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/var/www/pia/node_modules/which/which.js:80:29)
gyp verb `which` failed at /var/www/pia/node_modules/which/which.js:89:16
gyp verb `which` failed at /var/www/pia/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /var/www/pia/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb `which` failed python { Error: not found: python
gyp verb `which` failed at getNotFoundError (/var/www/pia/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/var/www/pia/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/var/www/pia/node_modules/which/which.js:80:29)
gyp verb `which` failed at /var/www/pia/node_modules/which/which.js:89:16
gyp verb `which` failed at /var/www/pia/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /var/www/pia/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb `which` failed stack:
gyp verb `which` failed 'Error: not found: python\\n at getNotFoundError (/var/www/pia/node_modules/which/which.js:13:12)\\n at F (/var/www/pia/node_modules/which/which.js:68:19)\\n at E (/var/www/pia/node_modules/which/which.js:80:29)\\n at /var/www/pia/node_modules/which/which.js:89:16\\n at /var/www/pia/node_modules/isexe/index.js:42:5\\n at /var/www/pia/node_modules/isexe/mode.js:8:5\\n at FSReqWrap.oncomplete (fs.js:154:21)',
gyp verb `which` failed code: 'ENOENT' }
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable \"python\", you can set the PYTHON env variable.
gyp ERR! stack at PythonFinder.failNoPython (/var/www/pia/node_modules/node-gyp/lib/configure.js:483:19)
gyp ERR! stack at PythonFinder.<anonymous> (/var/www/pia/node_modules/node-gyp/lib/configure.js:397:16)
gyp ERR! stack at F (/var/www/pia/node_modules/which/which.js:68:16)
gyp ERR! stack at E (/var/www/pia/node_modules/which/which.js:80:29)
gyp ERR! stack at /var/www/pia/node_modules/which/which.js:89:16
gyp ERR! stack at /var/www/pia/node_modules/isexe/index.js:42:5
gyp ERR! stack at /var/www/pia/node_modules/isexe/mode.js:8:5
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:154:21)
gyp ERR! System Linux 4.15.0-43-generic
gyp ERR! command \"/opt/node-v10.13.0-linux-x64/bin/node\" \"/var/www/pia/node_modules/node-gyp/bin/node-gyp.js\" \"rebuild\" \"--verbose\" \"--libsass_ext=\" \"--libsass_cflags=\" \"--libsass_ldflags=\" \"--libsass_library=\"
gyp ERR! cwd /var/www/pia/node_modules/node-sass
gyp ERR! node -v v10.13.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
Build failed with error code: 1"
Hi,
Just a question why the line of cnil-pia.conf is root /var/ww/pia/dist/; rather than root /var/www/pia/dist/pia/?**
Thx for your answer.
First of all, thank you for all your work. The tool looks amazing and it's great that people are giving their time to make it even better. The instructions where clear and I got the PIA site running quickly. But when I want to start a new PIA the site won't continue and my docker console keeps outputting:
cnil-pia-back_1 | standard_init_linux.go:190: exec user process caused "no such file or directory".
I first thought it was the connection between the front and backend, but analyzing the startup log more clearly shows me this:
docker-compose up
Starting piadocker_database_1 ... done
Starting piadocker_cnil-pia-front_1 ... done
Starting piadocker_cnil-pia-back_1 ... done
Attaching to piadocker_cnil-pia-front_1, piadocker_database_1, piadocker_cnil-pia-back_1
database_1 | 2018-04-21 21:44:35.630 UTC [1] LOG: listening on IPv4 address "XXXX", port XX
database_1 | 2018-04-21 21:44:35.630 UTC [1] LOG: listening on IPv6 address "::", port XX
database_1 | 2018-04-21 21:44:35.640 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
database_1 | 2018-04-21 21:44:35.666 UTC [20] LOG: database system was shut down at 2018-04-21 21:44:27 UTC
database_1 | 2018-04-21 21:44:35.677 UTC [1] LOG: database system is ready to accept connections
cnil-pia-back_1 | standard_init_linux.go:190: exec user process caused "no such file or directory"
piadocker_cnil-pia-back_1 exited with code 1
cnil-pia-back_1 | standard_init_linux.go:190: exec user process caused "no such file or directory"
Am I missing something? Are there more things I need to setup correctly in docker for it to work? (deamon or proxy or....?) And do I correctly setup the connection to the backend by setting it to http://localhost:3000?
Thank you for your time and effort!
I'm running docker-compose with all from this repo. I get the backend and frontend running. The backend is accessible via http://localhost:3000. Calling the frontend via http://localhost:8080 I get a redirect to http://localhost:8080/app/explorer.html and a 404 error from nginx.
Any hint's for further debugging?
I have the same problem as #18 .
Hello,
I tried to build the stack today with docker compose up -d but it failed at the front end
> [pia-docker_cnil-pia-front 4/13] RUN /usr/bin/npm install npm@latest -g && /usr/bin/npm install --unsafe-perm -g node-sass && /usr/bin/npm install -g @angular/cli:
#22 25.98 /opt/node-v10.16.0-linux-x64/bin/npx -> /opt/node-v10.16.0-linux-x64/lib/node_modules/npm/bin/npx-cli.js
#22 25.98 /opt/node-v10.16.0-linux-x64/bin/npm -> /opt/node-v10.16.0-linux-x64/lib/node_modules/npm/bin/npm-cli.js
#22 26.63 + [email protected]
#22 26.63 added 66 packages from 31 contributors, removed 236 packages and updated 190 packages in 24.939s
#22 27.09 (node:26) ExperimentalWarning: The fs.promises API is experimental
#22 35.61 npm WARN EBADENGINE Unsupported engine { package: '[email protected]',
#22 35.61 npm WARN EBADENGINE required: { node: '>=12' },
#22 35.61 npm WARN EBADENGINE current: { node: 'v10.16.0', npm: '7.19.1' } }
#22 48.95 npm WARN deprecated [email protected]: this library is no longer supported
#22 50.78 npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
#22 51.21 npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
#22 57.60 npm ERR! code 1
#22 57.61 npm ERR! path /opt/node-v10.16.0-linux-x64/lib/node_modules/node-sass
#22 57.61 npm ERR! command failed
#22 57.61 npm ERR! command sh -c node scripts/build.js
#22 57.61 npm ERR! Building: /opt/node-v10.16.0-linux-x64/bin/node /opt/node-v10.16.0-linux-x64/lib/node_modules/node-sass/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
#22 57.61 npm ERR! gyp info it worked if it ends with ok
#22 57.61 npm ERR! gyp verb cli [ '/opt/node-v10.16.0-linux-x64/bin/node',
#22 57.61 npm ERR! gyp verb cli '/opt/node-v10.16.0-linux-x64/lib/node_modules/node-sass/node_modules/node-gyp/bin/node-gyp.js',
#22 57.61 npm ERR! gyp verb cli 'rebuild',
#22 57.61 npm ERR! gyp verb cli '--verbose',
#22 57.61 npm ERR! gyp verb cli '--libsass_ext=',
#22 57.61 npm ERR! gyp verb cli '--libsass_cflags=',
#22 57.61 npm ERR! gyp verb cli '--libsass_ldflags=',
#22 57.61 npm ERR! gyp verb cli '--libsass_library=' ]
#22 57.61 npm ERR! gyp info using [email protected]
#22 57.61 npm ERR! gyp info using [email protected] | linux | x64
#22 57.61 npm ERR! gyp verb command rebuild []
#22 57.61 npm ERR! gyp verb command clean []
#22 57.61 npm ERR! gyp verb clean removing "build" directory
#22 57.61 npm ERR! gyp verb command configure []
#22 57.61 npm ERR! gyp verb find Python Python is not set from command line or npm configuration
#22 57.61 npm ERR! gyp verb find Python Python is not set from environment variable PYTHON
#22 57.61 npm ERR! gyp verb find Python checking if "python3" can be used
#22 57.61 npm ERR! gyp verb find Python - executing "python3" to get executable path
#22 57.61 npm ERR! gyp verb find Python - "python3" is not in PATH or produced an error
#22 57.61 npm ERR! gyp verb find Python checking if "python" can be used
#22 57.61 npm ERR! gyp verb find Python - executing "python" to get executable path
#22 57.61 npm ERR! gyp verb find Python - "python" is not in PATH or produced an error
#22 57.61 npm ERR! gyp verb find Python checking if "python2" can be used
#22 57.61 npm ERR! gyp verb find Python - executing "python2" to get executable path
#22 57.61 npm ERR! gyp verb find Python - "python2" is not in PATH or produced an error
#22 57.62 npm ERR! gyp ERR! find Python
#22 57.62 npm ERR! gyp ERR! find Python Python is not set from command line or npm configuration
#22 57.62 npm ERR! gyp ERR! find Python Python is not set from environment variable PYTHON
#22 57.62 npm ERR! gyp ERR! find Python checking if "python3" can be used
#22 57.62 npm ERR! gyp ERR! find Python - "python3" is not in PATH or produced an error
#22 57.62 npm ERR! gyp ERR! find Python checking if "python" can be used
#22 57.62 npm ERR! gyp ERR! find Python - "python" is not in PATH or produced an error
#22 57.62 npm ERR! gyp ERR! find Python checking if "python2" can be used
#22 57.62 npm ERR! gyp ERR! find Python - "python2" is not in PATH or produced an error
#22 57.62 npm ERR! gyp ERR! find Python
#22 57.62 npm ERR! gyp ERR! find Python **********************************************************
#22 57.62 npm ERR! gyp ERR! find Python You need to install the latest version of Python.
#22 57.62 npm ERR! gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
#22 57.62 npm ERR! gyp ERR! find Python you can try one of the following options:
#22 57.62 npm ERR! gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
#22 57.62 npm ERR! gyp ERR! find Python (accepted by both node-gyp and npm)
#22 57.62 npm ERR! gyp ERR! find Python - Set the environment variable PYTHON
#22 57.62 npm ERR! gyp ERR! find Python - Set the npm configuration variable python:
#22 57.62 npm ERR! gyp ERR! find Python npm config set python "/path/to/pythonexecutable"
#22 57.62 npm ERR! gyp ERR! find Python For more information consult the documentation at:
#22 57.62 npm ERR! gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
#22 57.62 npm ERR! gyp ERR! find Python **********************************************************
#22 57.62 npm ERR! gyp ERR! find Python
#22 57.62 npm ERR! gyp ERR! configure error
#22 57.62 npm ERR! gyp ERR! stack Error: Could not find any Python installation to use
#22 57.62 npm ERR! gyp ERR! stack at PythonFinder.fail (/opt/node-v10.16.0-linux-x64/lib/node_modules/node-sass/node_modules/node-gyp/lib/find-python.js:302:47)
#22 57.62 npm ERR! gyp ERR! stack at PythonFinder.runChecks (/opt/node-v10.16.0-linux-x64/lib/node_modules/node-sass/node_modules/node-gyp/lib/find-python.js:136:21)
#22 57.62 npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/opt/node-v10.16.0-linux-x64/lib/node_modules/node-sass/node_modules/node-gyp/lib/find-python.js:179:16)
#22 57.62 npm ERR! gyp ERR! stack at PythonFinder.execFileCallback (/opt/node-v10.16.0-linux-x64/lib/node_modules/node-sass/node_modules/node-gyp/lib/find-python.js:266:16)
#22 57.62 npm ERR! gyp ERR! stack at exithandler (child_process.js:301:5)
#22 57.62 npm ERR! gyp ERR! stack at ChildProcess.errorhandler (child_process.js:313:5)
#22 57.62 npm ERR! gyp ERR! stack at ChildProcess.emit (events.js:198:13)
#22 57.62 npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
#22 57.62 npm ERR! gyp ERR! stack at onErrorNT (internal/child_process.js:415:16)
#22 57.62 npm ERR! gyp ERR! stack at process._tickCallback (internal/process/next_tick.js:63:19)
#22 57.62 npm ERR! gyp ERR! System Linux 5.4.72-microsoft-standard-WSL2
#22 57.62 npm ERR! gyp ERR! command "/opt/node-v10.16.0-linux-x64/bin/node" "/opt/node-v10.16.0-linux-x64/lib/node_modules/node-sass/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
#22 57.62 npm ERR! gyp ERR! cwd /opt/node-v10.16.0-linux-x64/lib/node_modules/node-sass
#22 57.62 npm ERR! gyp ERR! node -v v10.16.0
#22 57.62 npm ERR! gyp ERR! node-gyp -v v7.1.2
#22 57.62 npm ERR! gyp ERR! not ok
#22 57.62 npm ERR! Build failed with error code: 1
#22 57.89
#22 57.89 npm ERR! A complete log of this run can be found in:
#22 57.89 npm ERR! /root/.npm/_logs/2021-07-09T10_06_58_380Z-debug.log
------
failed to solve: rpc error: code = Unknown desc = executor failed running [/bin/sh -c /usr/bin/npm install npm@latest -g && /usr/bin/npm install --unsafe-perm -g node-sass && /usr/bin/npm install -g @angular/cli]: exit code: 1
It is probably a duplicate of #5, but indeed I have had experience with such kind of problem related to node-sass. Shortly, both nodejs and node-sass must be kept up to date simultaneously. I used the master branch, so I could not exactly find where the change was committed.
We would like to provide additional fix. I suggest to upgrade to node 14 and check if node-sass is definitely required or not. And, in such case, provide/force the matching version. At the moment I am writing, I don't even know if node-sass is even required for the build. A number of projects I have seen do not really depend on node-sass despite having it in the devDependencies.
Hi, how can i configure LDAP-Authentication in PIA?
First of all thanks for your work, I was wondering if there is a way to implement authentication for the Frontend and for the Backend link that is not HTTP_AUTH
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.