Alpine requires coreutils to get timestamp in microseconds #104
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
|
Thank you so much, looks really good. The README has a part with the needed dependencies, I will add that also there. Since you are using alpine: Did you install gawk, or which package did you use? |
|
Alpine includes awk from busybox: https://wiki.alpinelinux.org/wiki/Awk |
|
ty, updated |
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.
Fixes #103
The cause was that the timestamp only had a precision of seconds, not microseconds.
Debugging log statements:
The solution is to install
coreutilsif you are using an Alpine image.In this PR I included a hint in the README and a check in the script if the timestamp has enough accuracy.
Not sure if the check is ok for you in the way I implemented it (checking the number of digits).