The difficulty of a workaround is irrelevant for the nature of the problem. Also as the article mentions this is undocumented behaviour, so unless rustc/cargo builds everything in containers by default this workaround should not be required.
And while I'm not an expert in GDPR details it is still very problematic as the file path to the compiled project could contain an arbitrary selection of very personal information that would then be leaked.
Sure you can build it in a container, you could also run a car assembly line in a cleanroom. It's just ridiculous to have that as requirement to not secretly leak paths.
But in any case, it wouldn't be rustc distributing your built code.
it's equivalent to saying that your self-hosted Postfix servers are violating GDPR because they includes information about which devices your message passed through on your local network during delivery in the header.
This smells like bullshit to me, but I don't know enough about GDPR to say for sure. Can anyone comment?
edit: more broadly, can free software (ie: rustc), run on individual developer machines, actually run afoul of the GDPR somehow?