Blog

CommandBox Docker v3.4.0 Images Released

Jon Clausen June 07, 2021

Spread the word

Jon Clausen

June 07, 2021

Spread the word


Share your thoughts

CommandBox 3.4.0 Docker images released



Today we are pleased to announce the release of version 3.4.0 of our CommandBox Docker images, which bumps the CommandBox binary version to v5.3.1. This release primarily contains optimizations and updates to leverage the new environmental support options available in CommandBox 5.3.0 and above.

Of note with this minor release, is that the image will no longer attempt to detect if a password has been set via the various environment and file-based mechanisms. Since servers run in Docker images bind the IP to all interfaces ( 0.0.0.0 ), the Server Profile is automatically set to production - which disables administrative access. Since the user of the BOX_SERVER_PROFILE environment variable is required to downgrade this profile to a less secure mode, along with the multitude of ways which admin passwords may be set, handling this in the container startup was unnecessary.

In addition, this version leverages native CommandBox support for environment variables as part of the server configuration and deprecates the use of variables which were redundant to the CommandBox versions. For more information on environment variables support, see the README

Changelog for this version:

[5.3.1/3.4.0] - 2021-06-04

Changed

  • Updates CommandBox binary to v5.3.1
  • Marked support for the following environment variables as deprecated, in favor of native CommandBox environment variables. Support for these variables will end in v4.0.0 of the image
  1. SERVER_HOME_DIRECTORY ( BOX_SERVER_APP_SERVERHOMEDIRECTORY )
  2. cfconfigfile ( BOX_SERVER_CFCONFIGFILE )
  3. CFENGINE ( BOX_SERVER_APP_CFENGINE )
  4. HEADLESS ( BOX_SERVER_PROFILE or ENVIRONMENT )
  5. SERVER_PROFILE ( BOX_SERVER_PROFILE )
  6. URL_REWRITES ( BOX_SERVER_WEB_REWRITES_ENABLE )
  7. DEBUG ( BOX_SERVER_DEBUG )
  • Eliminated random password generation on server startup, if a convention mechanism for changing was not detected. Since the server profile defaults to production, which disables the admin interface, this is no longer necessary

Fixed

  • Documentation updates and corrections

CommandBox Docker Hub Statistics

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