<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label. For the Community Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug For the Enterprise Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary When extracting cache that has symlinks the symlinked files throw a chmod error **WARNING: node_modules/@wek/clock: chmod node_modules/@wek/clock: no such file or directory (suppressing repeats)** it exists but is symlinked from a previous run. This then causes the following issue **npm WARN checkPermissions Missing write access to /builds/iues/wekwork-fe/node_modules/@wek/clock** ### Steps to reproduce (How one can reproduce the issue - this is very important) Install npm packages Create a symlink from node_modules Run the build Re-Run build (bug is here due to caching of the symlink) ### What is the current *bug* behavior? chmod is used when lchmod should be used to avoid this error ### What is the expected *correct* behavior? symlinks from cache do not create permission problems while extracting the cache ### Possible fixes use lchmod in the runner cache extraction instead of chmod, so that symlinks do not create this problem.