Migrate to Alpine, Update GoBGP #4
Closed
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
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 the required FROM was no longer supported (it was Ubuntu 17.10) as pointed out in issue #3 this was breaking the build process.
I've taken the option to move the base across to Alpine, which results in a somewhat quicker build and one that works at the moment.
The version of GoBGP has also been updated to the most recent that has been released at the moment - 2.8.0 up from 1.32.
In terms of testing, I've had it running for the last three hours with full BGP tables heading into it with a decent amount of updates and it's been fine for me but YMMV.