Check if running container was launched with compose v1 #619
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
lognaturel
approved these changes
Apr 2, 2024
|
I agree with the approach and have also verified the command. I don't think we need further verification than that. |
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.
As shown at https://forum.getodk.org/t/how-to-upgrade-central-from-v1-5-3-to-latest/45797/10
The check disk command doesn't work because even if you have compose v2 installed, if the container was launched with v1, it will have underscores in the name. This patch checks to see if there is a running container with underscores and returns a 1 or 0.
I haven't tested this on a real system, but I have verified the individual docker and grep commands work as expected.