-
Notifications
You must be signed in to change notification settings - Fork 25
Letting the container run with non-root privilegues creates ? directory #11
Comments
Hi manuel, thanks for the report! I was able to reproduce in my environment. With
|
I noticed that without the |
Exactly. In the Debian container images I build, I usually don't use https://gitlab.com/manuel_wagesreither/bora-proj/-/blob/master/docker/entrypoint.sh#L9 |
I forked your repo and tried to add the solution discussed above. Unfortunately building the docker image fails with |
I am now preparing to address this issue, so this is very helpful. Thank you :)
su-exec does the same thing and is available in the main repos. It looks nice. |
I made a pull-req. Any comments are appreciated :) You can explicitly pass UID and GID using environment variables. |
Avoid having ownership issue when using Docker Volumes (fix #11)
If you want to discuss this further, feel free to reopen it. Thanks for your contribution! |
Hi miy4,
thanks for creating this project, we're using it to create deployment diagrams of our CI pipeline.
We noticed when letting the container run with normal privilegues, that is, like so
it creates an empty
?
directory next to the PNG.Just wanted to make you aware of this, thought you might be interested in hearing about this.
Best regards,
Manuel
The text was updated successfully, but these errors were encountered: