You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if I just use "chgrp -R www-data src" it would use the groupID of my Host System. And if there is no webserver installed?... How would you know that the groupId is the same?
Maybe as Step 0 "how to get container name" docker ps
Step 1 should be to connect to the container using ssh (docker exec -it CoNtAiNerNaMe /bin/bash)
Step 2 is to run command on host system "id www-data" to get the ID. (in my case it was 33 so maybe you can simply change www-data to 33, if it gets the same ID every time.)
and now we can use "chgrp -R 33 src"
The text was updated successfully, but these errors were encountered:
thank you for this and your kind words
didnt see this issue in the "docs repo" here :) sorry
regarding your questions and ideas:
"chgrp"...haha yeah...so it just changes to id "33" which is then used on both systems.
as far as i know www-data should always be 33...at least thats what I think and always thought :D
so to just change it to the id instead of the name, because the host doesnt know it, if no werbserver is installed.
thats what you mean right?
Thanks for supplying such an easy to use dev environment.
I just want to mention, that the part here is not correct:
https://docs.dockware.io/tips-and-tricks/how-to-use-bind-mounting#3.-set-permissions
if I just use "chgrp -R www-data src" it would use the groupID of my Host System. And if there is no webserver installed?... How would you know that the groupId is the same?
Maybe as Step 0 "how to get container name" docker ps
Step 1 should be to connect to the container using ssh (docker exec -it CoNtAiNerNaMe /bin/bash)
Step 2 is to run command on host system "id www-data" to get the ID. (in my case it was 33 so maybe you can simply change www-data to 33, if it gets the same ID every time.)
and now we can use "chgrp -R 33 src"
The text was updated successfully, but these errors were encountered: