Affects Version/s: None
Fix Version/s: None
As always, please forgive the terseness of this description. I have not had time to polish it.
This page should be separated into a main page explaining the relative merits of the various approaches, and then subpages for each procedure. It is very easy to lose your place in it and perform steps for a completely different procedure.
I executed the Without a Reverse Proxy procedure and failed per ticket 80720. In this procedure I have the following comments:
- The curl command is not a conclusive test of whether the docker repository works
- docker login refuses the -p option. I worked around this by not using it.
- The instructions say, "Login to repository docker-virtual," but I do not see how I am logging in to "docker-virtual" without mentioning "docker-virtual" in the URL. The wording raises doubts, so if I fail, I must try the URL with and without my Docker virtual repository name.
I abandoned Without a Reverse Proxy because it did not work.
Next, I tried The Subdomain Method.
- This is repeated in Docker Reverse Proxy Settings, but the instructions are different. Which do I follow?
- The procedure for creating a self-signed certificate is not mentioned here. It is mentioned in The ports method.
First, you need to create a self-signed certificate for NGINX as described here for Ubuntu.