README: Add a troubleshooting section for environment variable problems #145
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
…rt because of unset environment variables
|
This would have saved me 15 minutes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What ?
Add a troubleshooting section to the README.md file so people who fail to launch their Docker container have a quick fix on the main documentation.
This is meant to be temporary. This solution is inelegant but may help people who are easily discouraged by the technical aspect of docker. Credit goes to Youtube user adamj50010 for providing this command line to help people in a comment section.
Why ?
I had this issue myself and found out on the tutorial videos that a significant amount of non-developer people have had this problem as well.