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

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.

That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.

Jacob Beers
Jacob Beers
June 04, 2026