Hello all. My ACF/Lucee experience is almost all typical OS installation methods. I'm spinning up a new, single site server, and would like it to be containerized for portability. I'm aware there's a CommandBox method out there, but I was hoping that I could just use native Lucee images with ngnix and MySQL on Docker Compose. But this is much harder than anticipated. Am I missing some great tutorial out there that could have saved me hours? Google Search has failed me and I'm not finding anything about Docker or even Lucee 6 in the Lucee docs. Here's my very basic compose file, but I can't even seem to access the admin UI. (I do get a promising 404 Not Found ngnix error when I go directly to the IP in the browser. Almost all the information I have found out there is quite old. Am I still stuck with having to create a custom Lucee image based upon the image defined below? Seems there should be a much more straight forward way with what I thought was quite popular?

services:
  lucee-nginx:
    image: lucee/lucee:6.0.3.1-nginx
    environment:
      - LUCEE_ADMIN_PASSWORD=changeme
    volumes:
      - ./www:/var/www # first part is host path, second part is container path
      - ./lucee/logs:/opt/lucee/server/lucee-server/context/logs
    ports:
      - "80:80"   # nginx
      - "443:443" # nginx
    restart: unless-stopped

CommandBox and Docker are not mutually excusive. The Ortus images use CommandBox inside of them. I find them to be quite a lot easier to use given the bundled functionality they have like CFConfig, a single JSON file for pretty much all server config, a much more powerful web server out-of-the-box (so you don't need NGinx, etc) and the ability to configure anything and everything with env vars, not just a few things.

Thanks @bdw429s. You just gave me a different perspective. It's not the one I had in my head, but so far appears to be the most viable. Thanks as always! I'll give it a shot.

@Chris Tierney -- I did a few presentations for the MMCFUG over the years that cover exactly this.

a separate reverse proxy for the app to help simplify load balancing

We've found (at Ortus) Docker Swarm to be the fastest, simplest, easiest way to get really nice load balancing up and going. I'm not neccessarily saying it's simple in general, but it's much simpler IMO than Kubernetes, and some of NGinx's load balancing features are paid features

Awesome guys. Yeah, accessing the admin in this scenario would be more for troubleshooting/looking for configs. I'm a UI guy. But understand it's not permanent in this case. One thing I did notice though is 6, opposed to -5, has a different directory structure as it no longer has web context. Minor thing, but no documentation.

We don't run Nginx inside the containers, but we do run a single instance outside of docker just for simplicity, one place to terminate the certs, serve static files, and put up a maint page if docker is down entirely

ah, I see. yeah I wouldn't turn it on. I only bring it up because of the volumes in the compose config.

@Chris Tierney -- that is correct. The default for Lucee 6 is for a single context (Lucee 4 and 5 were multi-context by default). But check out my videos and the related github projects. I have some skeleton projects there that can be useful to launch a new server with a DB, Reverse Proxy and Lucee in a docker compose setup.

We run nginx for ingress and then each container has nginx and in our case undertow which is the same as command box uses for what it’s worth I’m quite interested in https://world.hey.com/dhh/kamal-1-0-5304ff9e for personal projects though in pixl8 land we use Kubernetes