Blog

Jon Clausen

October 31, 2017

Spread the word


Share your thoughts

CommandBox 3.8 Docker image released



Today we released our 3.8 series of docker images ( current source version 2.1.0 ) which include a number of improvements and enhancements.

Change Log

  • Updates to CommandBox v3.8+
  • Adds support for Docker secrets
  • Adds casing aliases for environment variables
  • Adds new opinionated password security
  • Updates to runtime output for clarity
  • Changes image for alpine build to prevent CommandBox errors when installing dependencies

Security Enhancements

Upon container start, if no mechanism is detected for specifying the administrative passwords for the CFML engine (i.e. - CFConfig, custom server home, or environment variables ), a random password is generated. This prevents the image from using a predictable default. This password is available in the console output like so:

WARN: Configuration did not detect any known mechanisms for changing the default password.  Your CF engine administrative password has been set to: VxnrV816IFaHG0CmNemO251tihWeHZGwcLUJBurzj75y9vRwT7EqdFed9cWu2fIRvUn0pWVIINmoa34g

Docker Secrets

The image now provides support for secrets expansion when using Docker secrets in your singular, swarm, or stack deployment.

To employ the use of secrets in your runtime environment, you may map environment variables to secrets using the following syntax: MYVAR={{DOCKER-SECRET:docker_secret_name}} . Upon container start any environment variables containing these placeholders will expand the secrets and derive their values from the contents of the secret file.

Enjoy and happy coding!

Add Your Comment

Recent Entries

Inherited a CFML Application With Few Tests? Here’s Where to Start!

Inherited a CFML Application With Few Tests? Here’s Where to Start!

You need to change an application that has been running for years.

It might be a ColdFusion customer portal, a Lucee application supporting internal operations, or a CFML system your team is preparing to modernize. People depend on it, but some of its behavior lives in old tickets, scattered documentation, and the memory of whoever has supported it longest.

Now a release is approaching. You know more testing would help. The difficult part is deciding where to begin without putting every other priority on hold.

Start with one important workflow and build evidence around what it needs to do.

Explore Ortus Quality Assurance Services

Maria Jose Herrera
Maria Jose Herrera
October 27, 2026
Your ColdFusion Upgrade Passed. Did Your Business Workflows?

Your ColdFusion Upgrade Passed. Did Your Business Workflows?

The server restarted. The administrator shows the expected version. Your homepage loads, and a few familiar screens look fine.

Would you tell the business the upgrade is complete?

Consider an illustrative scenario: a customer submits an order after an upgrade. The application saves it and displays a confirmation page. But the confirmation email never arrives, and the scheduled process that sends the order to fulfillment has not completed.

From the browser, the transaction...

Maria Jose Herrera
Maria Jose Herrera
October 22, 2026