Thanks Jay,
The container was starting.. I could use docker top to see nginx running inside the container and that instance is what was giving the http error 502 “bad gateway”. I confirmed by stopping the container and then getting connection refused, so the container was running.. but discourse was failing to run properly.
Are you saying though that using the launcher utility it should start the discourse application inside the container? Or would that need to be executed from within the container itself?
Sorry for my ignorance here.