For example: Note: Your API Key can be found by navigating to Artifacts > your-generic-remote-repository > Set Me Up button. Set the sass_binary_site parameter to the generic remote repository you just created. On the repository's Advanced configuration page, scroll down and tick the Bypass HEAD Requests checkbox (to allow Artifactory to send GET requests without first issuing a HEAD request).Ħ. Create a generic remote repository, which proxies the following URL: ĥ. Run the following commands: npm config set registry npm login4. In your Artifactory UI, navigate to Artifacts > npm-remote > Set Me Up button:ģ. Then, do the following:ġ. Create an npm remote repository and set the following URL: Ģ. If you'd like to download and cache such packages to your Artifactory server, you'll first need to have node.js and npm installed on your local server. Some will even save and cache these packages for future reference. docker-compose version 1.15.Many organizations use the node-sass packages in their day-to-day operations. How should I configure the proxy for the build of this image in docker-compose ? I've tried several tutorials, but I did not succeed. Npm ERR! /root/.npm/_logs/T15_32_58_226Z-debug.logĮRROR: Service 'node1' failed to build: The command '/bin/sh -c npm update' returned a non-z Npm ERR! A complete log of this run can be found in: Npm ERR! network 'proxy' config is set properly.
Npm ERR! network If you are behind a proxy, please make sure that the Npm ERR! network In most cases you are behind a proxy or have bad network settings. Npm ERR! network This is a problem related to network connectivity.
Npm ERR! network tunneling socket could not be established, cause=connect ECONNREFUSED 127.0 Step 8/12 : RUN npm config set https-proxy -> Running in 3d9376ff8574 Removing intermediate container 1d9af892155c Step 7/12 : RUN npm config set proxy -> Running in 1d9af892155c Removing intermediate container f84cd3c05903 Npm WARN using -force I sure hope you know what you are doing. Removing intermediate container d1121964dbe4 Step 2/12 : MAINTAINER Douglas Quintanilha -> Using cache The problem is that when I try to run the build, an error occurs because of this proxy configuration: docker-compose build Ond 10.100.5.107 is the ip of my machine that serves as proxy on the 3128 port, without authentication required. So I added the commands: RUN npm cache clean -f To build my service, I have Dockerfile below: FROM node:latestĪs I use a corporate proxy, I researched how to tell you how to build this image, and I checked that this would be possible with npm config. To start testing, I created only one service in this file docker-compose.yml : version: '3'ĭockerfile. I am creating a docker-compose file to upload a multi-node system.
0 kommentar(er)
