New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config path of docker container can't be mapped #2196
Comments
Could you reproduce it with the mentioned commands locally at your machine? Or is this only a problem at my machine? |
@Disane87 I'll give it a try on windows and ubuntu. I'll post here my results when I'm done. |
ok great, thank you in advance! :) |
Any updates on this? If not, how can I assist you to get a solution? |
Please try with
;-) I had to install windows |
If you add |
Oh totally forgot it, shame on me. Will try it later :) enjoy Father's Day! |
This means the config file was not found. I did manage to map the config on Windows 10 and works fine using the same script to shared (file within config file must be named |
Unraid is a server software for creating NAS/Server systems. It's a cheap hypervisor for homelabs. This is where all my dev dockers are running. But what I don't understand is why this image is running on your windows and not on mine? I use the same command to start the container |
Just tested it again with your command on windows. It's not working when I want to map the conf folder. All other folders are ok. |
It's listed there, I wonder why does not work for you. Maybe someone else with Windows can give it a try @verdaccio/kubernetes @verdaccio/collaborators |
I guess this is a general issue since this even occurs on my unraid (linux machine) too. But this is totally against your observation that this fix is working on your windows machine. This is pretty strange. |
same issue for me also |
Please try the custom tag image I posted above (possible fix) |
you mean this? |
yes |
already tried it.but didn't work |
@juanpicado which version of docker are you using?
This is my version. Maybe an version issue? BTW: My windows system was only a system to check if the problem is reproducable on other systems. The main system where it should run is a linux one. |
share context please what command are you running and exact output, versions etc. |
Docker version 20.10.6, build 370c289 (Windows 10) |
Wow, this is really pretty weird. |
I just tried on a clean ubuntu installation, works for me using
|
Thank you! Do you have the created I updated docker to the latest version on my windows only for reference) and the following command, it's one by one identical with yours (only the username is changed) is not working:
|
The file must be there. (It is not created automatically) |
Aaaaah. I guess this is the issue. I actually anticipated this file would be created automatically. LIke the default config when you start it via npm. And now it's working... Would this be a good shot for the docker docs? I've read this section very carefully but I couldn't find a hint for this. |
:) be my guest repo 'verdaccio/website' hint: read contributions guideline. |
Just created a PR. It's my first contribution ever, so don't be so hard with me. |
@juanpicado You can consider this a closed. Thank you for your patience and assistance :) |
i have got it fixed after i added the config.yaml to my mapped folder, now i can't push the packages its' getting errors like that on server
on Local
|
command i ran |
You should open a separate issue for your publish problem, since there is no connection between the startup problem and you current issue :) |
If I want to run verdaccio on my unraid server, I can't map the folders
/config/
to a host folder. If I want to map them, the container won't start. There are no logs.The same occurs when I want to start the start the container on my Windows 10 system with WSL2 by following command:
If I run the container without the port mapping, it starts flawlessly by this command:
The container should start with mapped
/config/
folder.Unfortunatly there is currently nothing more I could share with you.
I guess there is something strange with the permissions itself. IMHO there are missing permission mappings for the
/config
at this line:verdaccio/Dockerfile
Line 44 in b02dab1
Unfortunatly I'm not that docker expert to debug this.
The text was updated successfully, but these errors were encountered: