Updating Consul DNS example #105
Open
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
Changing to a more recent vm box to keep the example up to date. Signed-off-by: Adam P Currier <[email protected]>
Updated image to be more current and modified the nginx plus setup to reflect practices today. Signed-off-by: Adam P Currier <[email protected]>
Signed-off-by: Adam P Currier <[email protected]>
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.
Updated the base images we are using, as the old ones are not working. Also modified the NGINX dockerfile to reflect current practices in our documentation: https://docs.nginx.com/nginx/admin-guide/installing-nginx/installing-nginx-docker/.
With these changes, the Consul DNS example with NGINX Plus is working again.