-
|
Your environment
Describe the bug Steps to reproduce Expected behavior Screenshots, Verdaccio server log, package manager log Configuration file Debugging output
Contribute to Verdaccio
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 16 replies
-
|
It looks like Verdaccio does not use your config. The docker image has a volume at |
Beta Was this translation helpful? Give feedback.
-
|
Is this compoundly expected? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Your images are broken 🤷 It looks like this for me: |
Beta Was this translation helpful? Give feedback.
-
|
[2025/4/30 15:00:59] [root@sync verdaccio]# docker exec -it rsync-npm sh |
Beta Was this translation helpful? Give feedback.
-
|
The rest looks ok. Let's see the debug log (below). |
Beta Was this translation helpful? Give feedback.
-
|
Could you please add the Verdaccio log with DEBUG on so we see where it goes wrong?
Then start the server and post the log here. |
Beta Was this translation helpful? Give feedback.
-
|
i tried to reproduce it with a new 6.1.2 image from docker hub. Verdaccio works correctly and published packages are stored in Did you actually publish a package to Verdaccio? |
Beta Was this translation helpful? Give feedback.
-
|
I am using Verdacio as a proxy, npm install yarn --timing --registry http://172.17.0.3:4873 ， /The yarn package is available in opt/, but not in/verdaccio/storage/. However, there is yarn v1.22.22 available in opt/. |
Beta Was this translation helpful? Give feedback.
-
|
Almost. You are correct that the yarn package should be in However, there should also be the tar file for the latest yarn package in this folder (which is https://registry.npmjs.org/yarn/-/yarn-1.22.22.tgz). My guess is that this package is cached by npm locally and therefore not requested again. Try clearing the npm cache. The yarn installation in |
Beta Was this translation helpful? Give feedback.
-
|
我测试了下，是我的问题，因为我想用宿主机verdaccio目录直接映射到容器/verdaccio目录，但是实际上Dockerfile对/verdaccio/storage创建了volume，所以再怎么挂载都没用和权限无关，所以需要指定-v 指定storage，如下
Edit: English 😉 I tested it and it turned out to be my problem, because I wanted to use the host verdaccio directory to map directly to the container /verdaccio directory, but in fact Dockerfile created a volume for /verdaccio/storage, so no matter how I mounted it, it was useless and had nothing to do with permissions, so I needed to specify -v to specify storage, as follows |
Beta Was this translation helpful? Give feedback.
我测试了下，是我的问题，因为我想用宿主机verdaccio目录直接映射到容器/verdaccio目录，但是实际上Dockerfile对/verdaccio/storage创建了volume，所以再怎么挂载都没用和权限无关，所以需要指定-v 指定storage，如下
docker run -d --name rsync-npm -p 4873:4873 \ -v /tmp/test/verdaccio/conf:/verdaccio/conf \ -v /tmp/test/verdaccio/storage:/verdaccio/storage \ --restart=always \ verdaccio/verdaccioEdit: English 😉
I tested it and it turned out to be my problem, because I wanted to use the host verdaccio directory to map directly to the container /verdaccio directory, but in fact Dockerfile created a volume for /verdaccio/storage, so no matter how I mounted it, it was useless and had nothing to do with permissions, so I needed to specify -v to specify storage, as follows