Add permissions to mirror user to fix Docker start failure (EAccess) #132
Conversation
This file contains 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
This commit grants the necessary permissions to the 'mirror' user to resolve a Docker start failure issue, specifically an access error (EAccess). It was found that this error was due to insufficient permissions for the 'mirror' user. By providing the appropriate permissions, Docker can now start without issues, thereby eliminating the error that was hindering its proper operation.
jeremylong
approved these changes
Feb 15, 2024
This was referenced Feb 15, 2024
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.
This commit grants the necessary permissions to the 'mirror' user to resolve a Docker start failure issue, specifically an access error (EAccess). It was found that this error was due to insufficient permissions for the 'mirror' user. By providing the appropriate permissions, Docker can now start without issues, thereby eliminating the error that was hindering its proper operation.