Remove sudo from build_and_check_circle_config#104
Open
andheiberg-babylonhealth wants to merge 1 commit into
Open
Remove sudo from build_and_check_circle_config#104andheiberg-babylonhealth wants to merge 1 commit into
andheiberg-babylonhealth wants to merge 1 commit into
Conversation
Interested to get your thoughts. I have a docker image that doesn't have sudo installed. So I can't rely on sudo. I wonder why this was setup in the first place, but it was presumably because the file permissions of your image were more sensibly locked down. For now I will install sudo on the CI image to get this to pass. Just curious to hear your thoughts.
Author
|
The other option for me is to install circleci cli my self and use install-circle-cli: false |
Owner
|
what if you make sudo a param?
|
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
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.
Interested to get your thoughts. I have a docker image that doesn't have sudo installed. So I can't rely on sudo. I wonder why this was setup in the first place, but it was presumably because the file permissions of your image were more sensibly locked down.
For now I will install sudo on the CI image to get this to pass. Just curious to hear your thoughts.