Updated dockerfile with options for including your own root certificate and deploying your container to an Azure App Service. #269
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
…te and deploying your container to an Azure App Service.
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.
While deploying this privately, I encountered a few issues which caused some significant trouble. Two of these are addressed by updating the dockerfile, and I hope this PR can save others some time and headaches.
My modifications are commented out by default and are opt-in configuration decisions.
Using a Proxy / SWG / etc. which intercepts SSL
This scenario requires uploading your own root certificate to the container and configuring Node to trust it. This modification was based on this Stack Overflow conversation.
Custom Container + Azure App Service
Our solution used the above custom container deployed to an Azure App Service via an Azure Container Registry. The container would continually get shut down due to failing to respond to HTTP ping requests. Based on this somewhat related tutorial, I tried switching the HOSTNAME environment variable value to 0.0.0.0. This instantly solved the problem.