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
hoyosjs
changed the title
dotnet tools don't properly work in read-only FS deployments
dotnet tools don't work in read-only FS deployments due to tmp dependency
Jan 9, 2024
We have documented our dependency on /tmp or $TMPDIR and with that workaround our tools seem to work on RO filesystems (as far as I can tell). Perhaps we should link https://learn.microsoft.com/en-us/dotnet/core/diagnostics/diagnostic-port#default-diagnostic-port documentation to our global tool docs and specifically call out if /tmp isn't writable, then TMPDIR needs to be set in both the target process as well as the diagnostic tool.
Add a warning/error to dotnet-* tools when we detect that /tmp or $TMPDIR isn't writable.
Why does this only partially solves this issue? The initial description only talks about the System.CommandLine problem which is fixed by that PR. The title and Tom's comments may indicate there are other R/O /tmp problems. Can we list them?
System.Commandline tries to create a sentinel in tmp when registering for dotnet-suggest for their support of autocompletion support. This prevents usage of tools in read-only deployments.
The text was updated successfully, but these errors were encountered: