This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Running dotnet-monitor in a docker sidecar (not root) #7715
Labels
documentation
Improvements or additions to documentation
Documentation Request
Running dotnet-monitor in a docker sidecar container mode, when using non-root users (default for dotnet-monitor, and aspnet images).
I am adding dotnet-monitor to AWS ECS container, as a side-car. I'm unable to get dotnet-monitor to read the socket file from the app when running both as their default users. I understand that the default UID of aspnet and (I suppose) dotnet-monitor is 1000 (app).
This gives me Permission Denied from IpcSocket. Running them both as root does solve this problem, however I would like to drop down to the default permission set as recommend by Microsoft and the default containers.
I attach a normal Docker volume (non persistent) to both containers, and do not specify their UID when starting them. This gives me permission denied.
I've tried setting both their users to 'app', '1000', '1654', but none of these settings work.
What am I missing here? I feel like a little more documentation on this (mostly likely the default?) configuration would be very useful.
Previous documentation
Existing docker compose for this scenario
Configuration example
The text was updated successfully, but these errors were encountered: