Thanks for the suggestion Bilal!
In fact, last night I was able to access the Lucee administrator (it's a beautiful site) with the help of Geoff Bowers. I was trying to run the lucee/luce4-nginx docker container directly, which was really where I went wrong to begin with.
The correct approach, as it turns out, is really to only use the preconfigured lucee containers as boxes upon which you base your custom image. By creating a new image based on lucee/lucee4-nginx and adding the "configuration overrides" for nginx and lucee, I was able to access the administrator (at http://[docker_machine_ip]/lucee/admin/server.cfm) and create a new datasource, which in turn pointed to another docker container on port 3306. Then, I had a simple index.cfm file run a query and dump some data. Great!
At this point, I thought I was home free for running my app, but I still have two issues to work out:
- Upon pulling in the actual application code, I noticed that DI/1 is having issues trying to auto-discover the beans in my model. I've never had this problem before, so I'm trying to figure out why this is happening, and
- The mounting of volumes from my OSX host into the container is proving challenging since there are 3 layers to content with in the docker world when running on OSX or windows: 1) the host os (OSX), 2) the docker-machine (virtual linux machine for the docker engine to run in), and 3) the docker containers themselves. My goal is to get a volume from OSX to mount directly into the docker container, which as I said is proving challenging, but is perhaps outside the scope of this discussion.
Thanks everyone for your suggestions and help. I'm close!