Fix for weird issue with Nexus not able to resolve basic packages#483
Open
Fix for weird issue with Nexus not able to resolve basic packages#483
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Trying to clean room install a few things, and was getting very strange errors from pip trying to get authentication from a user when being run in docker compose build. Once I fixed that, the next error was that nexus did not have some basic packages, such as setuptools.
This PR uses Nexus repo as an extra package URL to work around the error. It may not be needed, as it could be something to do with the permissions changing for the nexus user/password but I am parking this here just in case.