我正在尝试启动我的 React docker 容器（https://github.com/AndrewRPorter/flask-react-nginx），但安装在发出各种警告后挂起。
我在 Ubuntu 上运行。我的直觉是某种网络干扰。我没有使用 VPN。
我的Dockerfile如下：
FROM node:12
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm install 2>&1
COPY . .
EXPOSE 3000
# start the development server
CMD ["npm", "start"]
我安装时得到的输出是：
npm WARN tarball tarball data for [email protected] (sha512-81PIMmVLnCNLO/fFOQxdQkvEq/+Hfpv24XNJfpyZhTRfO0QcmQIF/PgCa1zCOj2w1hrn12MFLyaJ/G0+Mxtfag==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for @testing-library/[email protected] (sha512-di1b+D0p+rfeboHO5W7gTVeZDIK5+maEgstrZbWZSSvxDyfDRkkyBE1AJR5Psd6doNldluXlCWqXriUfqu/9Qg==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-00ZMZUiHaJrNfk33guavqgvfJS30sLYf0f8+Srklv0AMPodGGHcoHgksZ3OThYnIvOd+8yMCn0YiEOogjlgsnA==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-8xOcRHvCjnocdS5cpwXQXVzmmh5e5+saE2QGoeQmbKmRS6J3VQppPOIt0MnmE+4xlZoumy0GPG0D0MVIQbNA1A==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for @typescript-eslint/[email protected] (sha512-W2YyMtjmlrOjtXc+FtTelVs9OhuR6OlYc4XKIslJ8PUJOqgYYAPRJhAqkYRQo3G4sjvG8jSodsNycEn4W2gHUw==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-EzJRHvwQyBiYrYqhyjW9AqM90dE4+s1/XtCfn7uWg6cS72zH+2VPFAlsnW0+W0cDi0XRjNKUMoJtpSi50+Ph6w==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for @testing-library/[email protected] (sha512-oZ0Ib5I4Z2pUEcoo95cT1cr6slco9WY7yiPpG+RGNkj8YcYgJnM7pXmYmorNOReh8MIGcKSqXyeGjxnr8YiZbA==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-K+Iayyo2LtyYhDSYwz5D5QdWw0hCacNzyq1Y821Xna2xSJj7cijoLLYmLxTQgcgZ9mC61nryMy9S7GRbYpI5Ig==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-CawzfGt9w83tyuVekn0GDPU9ytYtxyxyFZ3aSWROmnRRFQFT2BiPJd7jvRdzNDi6oLWaS2asMeYSNMjWTV4eNg==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-e4nWev8YzEVNdOMcNzNeCN947sWJNd43E5XvsJzbAL08kGc2frm1tQ32hTJslRS+H65LCb/AaUCYU7fjHCpDeQ==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-WuQETPMcW9Uf1/22HWUWP9lgsIC+KEHg2kozMflKjbeUtw9ujvFX6QmIfozaErDkmLWS9WEnEdEe6Uo9/BNTdQ==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-4paDGScNgZP2IXXilaffL9X7968RuvwlkK3xWtZRVqgd8SYNiVKRJvkFd1aqqEuPfN7E68ZHEp9hDj6lHj4Hyw==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-uIFtJElxJo29QC753JzhidoAhvp/e/Exezkdhfmt8AymWT6/5B7W1WmponYWkHk2eg6sONyTch0A3nkMPun3SQ==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-O901mfJSuTdwU2w3Sn+74T+RnDVP+FuV5fH8tcPWyqrseRAb0s5xOtPgCFiPOtLcyK7CLIJwPyD83ZqQWvA5ng==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for @testing-library/[email protected] (sha512-di1b+D0p+rfeboHO5W7gTVeZDIK5+maEgstrZbWZSSvxDyfDRkkyBE1AJR5Psd6doNldluXlCWqXriUfqu/9Qg==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for [email protected] (sha512-81PIMmVLnCNLO/fFOQxdQkvEq/+Hfpv24XNJfpyZhTRfO0QcmQIF/PgCa1zCOj2w1hrn12MFLyaJ/G0+Mxtfag==) seems to be corrupted. Trying one more time.
npm ERR! code EINTEGRITY
npm ERR! Verification failed while extracting @testing-library/[email protected]:
npm ERR! Verification failed while extracting @testing-library/[email protected]:
npm ERR! sha512-di1b+D0p+rfeboHO5W7gTVeZDIK5+maEgstrZbWZSSvxDyfDRkkyBE1AJR5Psd6doNldluXlCWqXriUfqu/9Qg== integrity checksum failed when using sha512: wanted sha512-di1b+D0p+rfeboHO5W7gTVeZDIK5+maEgstrZbWZSSvxDyfDRkkyBE1AJR5Psd6doNldluXlCWqXriUfqu/9Qg== but got sha512-Bf+V8vCdAtDbh2K4IVqKgtvkHNi23ZwxU3mYrjvvZtbgOEeMSTVwEo77cPeZBcGWnKUM8XDQjnHfy3ebg/ugKA==. (64745 bytes)
npm WARN tarball tarball data for @babel/[email protected] (sha512-BS9JKfXkzzJl8RluW4JGknzpiUV7ZrvTayM6yfqLTVBEnFtyowVIOu6rqxRd5cVO6yGoWf4T8u8dgK9oB+GCng==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for @babel/[email protected] (sha512-bC49otXX6N0/VYhgOMh4gnP26E9xnDZK3TmbNpxYzzz9BQLBosQwfyOe9/cXUU3txYhTzLCbcqd5c8y/OmCjHA==) seems to be corrupted. Trying one more time.
...
npm WARN tar ENOENT: no such file or directory, open '/usr/app/node_modules/autoprefixer/lib/hacks/flex-wrap.js'
npm WARN tar ENOENT: no such file or directory, open '/usr/app/node_modules/core-js/internals/array-buffer-native.js'
npm WARN tar ENOENT: no such file or directory, open '/usr/app/node_modules/core-js/internals/array-buffer-view-core.js'
npm WARN tar ENOENT: no such file or directory, open '/usr/app/node_modules/core-js/internals/array-buffer.js'
npm WARN tar ENOENT: no such file or directory, lstat '/usr/app/node_modules/@babel/types/lib/asserts/generated'
npm WARN tar ENOENT: no such file or directory, open '/usr/app/node_modules/lodash/fp/_convertBrowser.js'
使用不同的图像解决了我的问题。 尝试使用如下所示的较亮的图像。
FROM node:13.12.0-alpine
当要执行 docker run 时添加新标志，网络
docker run -t yourdockerhub/package --network=host .
我花了两个世纪的时间才发现，我想如果它挂在 npm install 上，它也对你有用。
我在 UI 容器中遇到了同样的问题。
尝试从容器中的 /usr/src/app 文件夹中删除 node_modules，然后重试。
如果您仍然遇到问题，请通过以下命令删除 UI 容器和图像。
Docker rmi IMAGE_ID
Docker rm CONTAINER_ID
然后再试一次。
即使没有任何区别，对我来说，将
--verbosenpm installRUN npm install --verbose