If you use nodejs provided by Red Hat, that's it! This will also make the registry trusted by your browser, and tools like curl/wget, openssl.Īdd the CA or self signed certificate to /etc/pki/ca-trust/source/anchors/. On Fedora/RHEL/CentOS/Debian/Ubuntu I would add it to the OS trust store, and configure yarn to use the OS trust store. '/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem', // CentOS/RHEL 7 '/etc/pki/tls/certs/ca-bundle.crt', // Fedora/RHEL 6

'/etc/ssl/certs/ca-certificates.crt', // Debian/Ubuntu/Gentoo etc. # update-ca-certificates - add the cert to /etc/ssl/certs/ca-certificates.crt bundle RUN apk update & apk add ca-certificates & rm -rf /var/cache/apk/*

# some base image don't have update-ca-certificates #copy custom cert, in current build directoryĬOPY zscaler-root-ca.crt /usr/local/share/ca-certificates/zscaler-root-ca.crt >yarn config set cafile path/to/ca-bundle.crt -gĭocker - yarn (same concept for others tool) >set NODE_EXTRA_CA_CERTS=/etc/ssl/cert.pem if npm invoke script to call node directly, npm config is not respected, two workgroundġ. >npm config set cafile path/to/ca-bundle.crt -g >git config -global http.sslCAInfo path/to/ca-bundle.crt >conda config -set ssl_verify path/to/ca-bundle.crt (or false to disable)

(if config is not set, use pip -cert or -trust-host each call) >pip config set global.cert path/to/ca-bundle.crt

Npm config set ca