Fix e2e:docker failure with "access denied" #6050
Merged
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.
Is this a bug report?
yes
Did you try recovering your dependencies?
Yes
Which terms did you search for in User Guide?
e2e, access denied, test-integrity
Environment
Steps to Reproduce
yarn && yarn e2e:docker
Expected Behavior
Tests should work, especially on the v2.1.1 branch.
Actual Behavior
Fails with this:
After dropping into an interactive terminal afterwards, it turns out that the
prefix
line of/home/node/.npmrc
is missing. I don't know why, but my system seems to be removing it at some point.As a fix, I've defined npm's prefix with an
NPM_CONFIG_PREFIX
environment variable instead, as per this docker-node guide. This has solved the problem and made the tests pass as expected.Related issues
At least one other person has recently encountered this same issue: