Use /etc/profile.d to set PATH for dotnet tools #1492
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Back in #628, I added
~/.dotnet/tools
to thePATH
using a relative path incontainerEnv
, so dotnet global tools would work regardless of the container user.While this worked for running dotnet global tools, it broke compatibility with
find -execdir
, which treats relative paths inPATH
as unsafe.This PR removes the relative path from
containerEnv
and instead adds a script to/etc/profile.d
that appends$HOME/.dotnet/tools
toPATH
for login shells. This preserves global tool functionality without compromising security.